Complex report

[jason_nevin]

I am writing a complex report which contains 18 subreports. I have been suffering problems all along with errors related to the number of databases that are open and seemingly the amount of memory being used. Essentially the report is all based on data from a single query but because it needs several different sections I've had to use subreports thus increasing the number of queries that are executed. This works when there is little data but as the report gets bigger I've been hitting problems outlined above. I've therefore decided to look at programming-based alternatives. Essentially I think I need to base my report on a recordset which I then store in a global array which I access from each subreport.

a) Does does this sound feasible or reasonable?

b) Does anyone have any tips or pointers on producing reports programmatically from a recordset array?

c) Does anyone have a better idea?

I'd be very grateful for your thoughts.

Regards

Jason.

 

[Pat Hartman]

If all the data is coming from the same query, why do you have 18 subreports? You can use the report's sorting and grouping properties to cause breaks at certain points in the data. For example, you can break on Company and even force a page change if you want.