>Bill,
>
>Exactly the justification for denormalizing. But denormalizing should not be taken lightly ro done before a fully normalized design is realized. You should use the calculations when printin reports so that regardless of anything that might cause a problem with synching the fields, the reports will alwys be consistent and driven from the details. This way accountants can easily make correcting entries.

I don't understand your last sentence. What does correcting entries have to do with denormalizing data?

I agree with you about only denormalizing AFTER creating a fully normalized design. But I do believe that being able to program calculations at the dbc level will cause the normalization rules to be rethought.