>>There are certain kinds of interface when 'calculated' column is not really calculated :), i.e. interface provides users with tools to make adhoc calculation and save result without caring how it was reached. For example, it may allow to apply random discounts to price, 5% (not right ?), ok then 5% more, 4% more etc. until 'final' result (i.e. satisfactory for a customer on phone) is reached. This way 'calculated' field should be saved, though I'm unsure if it's the case for this thread.
>
>Agree, but this is not calculated :-) this is USER DECIDED what the price must be. And in the report that will look terrible:
>

>Qty        Unit Price   Total
>-----------------------------
>10            10          45
>

>Grrrrrrrrrr
>Better add an additional column with discount where the user can add the discount and keep calculated coluln out of the table :-)

No, in your example custom price (and total based on it) would be a result of 'calculations', and report could show also unit price and some discount (really calculated) against unit price.
My point was that grid interface could have a column that is 'calculated', from interface standpoint, but data would be saved to table.