I thought that as long as the computed column was deterministic (something like total AS (Qty * Price)) then it would be calculated at INSERT or UPDATE time only and the column could be used as an index and then optimizable...
>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.
>
>John
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"