Bill,

Have you run the coverage profiler on your code to see exactly what takes the longest?


>Hi Cindy,
>It is just taking too long to keep re-calculating the totals for reports. There are 3 reports that the client runs several times a day to reflect current data, they run as many as 12 different calculations. It currently takes over 2 minutes to pull the data together for the one of the reports. Since he runs the report several times, I can't wait for a batch to be run at the end of the day. I'm hoping to create something that updates the totals as the detail is being edited. There are as many as 100 detail edits each day.
>
>
>>Bill,
>>
>>Can you say more about why you need to store totals rather than re-calculating them as necessary? There is no good way to be sure they are always correct if the Details table continues to change.
>>
>>That being said, if you have a denormalized database used for reporting I can see how you might want to select the totals and store them. But then you would be taking a snapshot of your data and using the batch process you described to update it each night or weekly or something like that.
>>
>>
>>>When I need to store totals in a different table (TOTALS.DBF) than the detail (DETAILS.DBF