Information I type in a form, doesn't show on the table

[Guest]

Help, all of the information I type into a form shows on the table such as
the client, address, phone, etc. However, none of the information that has
expressions shows on the table. Such as the total amount for tickets.
Example: The number of tickets shows, the cost of the ticket shows, but the
total doesn't show [#tickets]*[costoftickets].

Do I have to go into the table and enter this manually everytime I enter a
recordina form?

 

[fredg]

Help, all of the information I type into a form shows on the table such as
the client, address, phone, etc. However, none of the information that has
expressions shows on the table. Such as the total amount for tickets.
Example: The number of tickets shows, the cost of the ticket shows, but the
total doesn't show [#tickets]*[costoftickets].

Do I have to go into the table and enter this manually everytime I enter a
recordina form?

Access is working correctly.
Do NOT store calculated data.
As long as you have the cost of each ticket and the quantity stored in
the table, anytime you need the total simply re-calculate it, using
the same expression you use now.

 

[John Vinson]

Help, all of the information I type into a form shows on the table such as
the client, address, phone, etc. However, none of the information that has
expressions shows on the table. Such as the total amount for tickets.
Example: The number of tickets shows, the cost of the ticket shows, but the
total doesn't show [#tickets]*[costoftickets].

Do I have to go into the table and enter this manually everytime I enter a
recordina form?

Storing derived data such as this in your table accomplishes
three things: it wastes disk space; it wastes time (almost
any calculation will be MUCH faster than a disk fetch); and
most importantly, it risks data corruption. If one of the
underlying fields is subsequently edited, you will have data
in your table WHICH IS WRONG, and no automatic way to detect
that fact.

Just redo the calculation whenever you need it, either as a
calculated field in a Query or just as you're now doing it -
in the control source of a Form or a Report textbox.

If you're assuming that data must be stored in a table in order to
have it appear on a report - correct your assumption. It's wrong.

John W. Vinson[MVP]