>I think one of the first things you have to do is distinguish between issues of data integrity, consistiency, etc and issues of reporting. The goals of normalization are to reduce redundancy and encourage consistiency. All of this is at odds with reporting requirements which tends to make use of lots of summary values and calucations.
>
>Often, calculating the values on the fly is not a problem. However, at some point, performance starts to take a hit to the degree that waiting for the report to generate is a waste of time.
>
>So, do you violate rules of normalization for the purpose of reporting? If your online data entry tasks don't get hampered as a result, why not? It could be argued that in reality, you are not violating the 3rd normal form since these summary values are distinct data entities. I do this sort of thing all of the time.
>
>Adhering to any rule independent of the facts of the situation can get you in trouble. Often, it makes sense sense to deviate from the rules.

Thank you for your response, John. I'll let you know if I find a Salomonic solution.

Alex