>I'm a former Clipper programmer switch to VFP few years ago, I still keep my old Clipper style, when I tried to convert to SQLServer database, I asked another programmer for an advise. he said my database designed was bad, and it won't work with SQLServer database.
>
>The main issue with my design is I always keep calculated fields, which store how many stock onhand in store, warehouses, etc, while he said I shouldn't have any calculated fields, thus avoid record locking, if I want the figure I should recalculate them from the invoices. We have argued about this issue for a long time and I don't know who is right. I can't imaging how I can recalculate 100.000 items before printing a stock onhand report.
>
>I would like to ask for your opinion.

Here's one opinion...

I do rarely store calculated fields in tables, but only when response time demands are stringent and I have no other choice.
Why?... Because I run the risk of forgetting that such fields are there when doing 'regular maintenance' or other work that might indirectly impact such fields. 'Cause then I have REAL trouble on my hands.

I don't feel that your example even comes close to justifying storing calculated fields! A 100,000 item stock on-hand report will print in virtually the same amount of time, I hazard, whether you calculate at print time or not. specially given tody's processor speeds and RAM sizes.

One opinion... worth the electrons it's written with.


>
>John