We took a look at the diagnostic file you sent in, and the bottleneck for the report is the rendering process. This is mostly dependent on the factors that Doug mentions:
Other things to consider: the amount of memory in the workstation, how busy the server is, network traffic, etc. Also, will someone really read a 32,000 record, several thousand page report? Perhaps you should add a filter to the report to make it a more reasonable size.
[/quote]
In addition to investigating these things, you can also doublecheck the complexity of the report layout itself. Reducing the number of objects (for example, if you have graphics in the layout) can speed up this process. Also, if you are calling user defined functions from the layout, you may need to optimize the calculations being made.
Trevor
|