As posted almost every day in these newsgroups (please make a habit of
searching for an answer before posting) you should not store calculated
values. When you need that value, calculate it in your forms, reports, or
queries.
If you store it, and one of the numbers that make up the calculation change,
then what? Your number is now wrong.
Store the numbers that make up the calculation, not the calculation itself.
Possible, but almost always a bad idea. If you can calculate it then it
doesn't need to be stored. All your table needs is the data in the fields
that your expression uses as operands. Using those the calculated value can
always be derived on the fly and that is the fastest and best way to do it.
Well, lots of things are possible, but saving a value
calculated from two fields in a third field would be a
violation of data normalization rules. Without more
information, the "correct" thing to do is to perform the
calculation where ever you need to display the result.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.