relationship inderteminate---Fred?

Hello acss,

Nice to see you back after our precious exchange.

One of there rare exceptions to the "don't store the results of
calculations" is when the underlying number DO normally change, and you need
to store the "Old" result which was based on the old underlying values.

There are lots of reasons for this recommendation/"rule", and Beetle gave
just one of them as an example. But, even for that, "never say never"
For example, correcting an error.

Reason #2 is that it's a lot less work. If anybody makes a correction in
the underlying values, you have to make sure that the redo the total.

Long story short, about 95% of the time yo are better off not storing the
result of a calculation, and, instead, have the application calculate it at
time of need, and you are probably in the 95%

Sincerley,

Fred

Hi Fred,
Thanks for the support. After researching various sample data bases, I find
that the northwind DB is what i am trying to do in that in a one to many
scenario, the entry of an invoice and details items that lead up to the final
total, it is the detail items that are recorded as you state then using a
query /form /report totals are derived from these items. I find northwind as
an excellent template to customize yet i have a ways to go and hopefully my
ID wont be part of many postings, thanks again.

"Fred" wrote:

Hello acss,

Nice to see you back after our precious exchange.

One of there rare exceptions to the "don't store the results of
calculations" is when the underlying number DO normally change, and you need
to store the "Old" result which was based on the old underlying values.

There are lots of reasons for this recommendation/"rule", and Beetle gave
just one of them as an example. But, even for that, "never say never"
For example, correcting an error.

Reason #2 is that it's a lot less work. If anybody makes a correction in
the underlying values, you have to make sure that the redo the total.

Long story short, about 95% of the time yo are better off not storing the
result of a calculation, and, instead, have the application calculate it at
time of need, and you are probably in the 95%

Sincerley,

Fred