hope someone out there can help.... writing an access database (invoices
system for a small company I run) and have a printable invoice in 'forms'
(which doubles up as a parcel label & delivery note) and managed to
succesfully put together calculations using the control source / expression
builder (ie 'product 'a' multiplied by selling price gives a total of 'b''
etc )... however the database table is pretty useless as these calculation
totals do not appear in the table master... thus rendering reports / queries
also useless... any ideas?? at the moment the form shows the calculation to
be correct but the 'table' shows the calcs a zeros....
Rick Brandt - 27 Jul 2005 17:59 GMT
> hope someone out there can help.... writing an access database
> (invoices system for a small company I run) and have a printable
[quoted text clipped - 6 lines]
> any ideas?? at the moment the form shows the calculation to be
> correct but the 'table' shows the calcs a zeros....
Calculations do not belong in tables. Put the same expressions you have on
your form in a query and base your reports on the query. Those fields
should then be deleted from the table entirely.

Signature
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Tim Ferguson - 27 Jul 2005 18:17 GMT
> hope someone out there can help.... writing an access database
> (invoices system for a small company I run) and have a printable
[quoted text clipped - 6 lines]
> any ideas?? at the moment the form shows the calculation to be correct
> but the 'table' shows the calcs a zeros....
If you want anything printable, then it's better to use a report than a
form. Still, as long as you can create the data you want in a query, then
you can base the report or form on that query and the job is done.
Reports are very often based on joins and aggregates rather than simple
one-table recordsets.
For your purposes, I guess you would join the Customers table to the
Addresses table, and also to the Invoices table which would be joined to
the OrderLines table and thence to the Products table and the
CurrentPrices table. With a few GROUP BY and SUM() clauses thrown in too.
Or something like that.
Hope that helps
Tim F