I do that only in the case that it makes things run appreciably faster or makes the coding of something much easier. However, if it is at all possible that the total will get out of synch with the actual data, make sure you include a function to recalculate it.
Of course, since most of my work is against SQL Server these days I would actually define a calculated field in the table itself, Frank. Frank Cazabon On 31/10/2011 01:34 PM, MB Software Solutions, LLC wrote: > I've always calculating values on the fly but have recently seen an > application where for their case, they save/store the totals. I can see > this can be good where the calculations and long and intensive. > Wondered on others viewpoints on this to see what helps them decide when > to store totals. > > Thanks, > --Mike > _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
