Multiple Subreports and Performance Issues

[yosteevo]

I am using Crystal Reports 2008.
I have a report that is configured with multiple subreports that are linked to specific data groups within my database. I have about 100+ subreports within one main report.
This allows my laboratory to utilize one main report for all the various testing & reporting they do.

As I continue to add additional subreports to the configuration of this main report, it obviously slows down due to (most of the subreports making identical database queries) - returning similar/comparable results.

Since many of my subreport configurations are similar to each other, can I utilize one subreport for all configurations that utilize similar data graphs/layouts?

I tried using groups to sort the data by test group name so the similar testing groups would not get all mixed together. This did not work out and I could not get groups to effect subreports when the group is configured outside of the subreports.


Thanks for any help.
Stephen Waichulis

 

[Madawc]

Each call to a subreport involves a separate instance of accessing the database. I don't think it makes a huge difference if you have 100 separate subreports or find ways to call a single subreport on 100 different occasions.

It seems you've already tried the normal solution, grouping based on data collected by the main report. Maybe you should start a new thread explaining what you mean by

did not work out

Someone may be able to help.

It's also possible that you could group within some of the subreports. If one subeport does the same job as 3 or 4 of those you have, this would speed processing.

If you use SQL, you might also be able to create an SQL command. This can do several separate selections and merge them into a single file.

Madawc Williams (East Anglia, UK). Using Crystal 2008 with SQL and Windows XP

 

[yosteevo]

Thanks Madawc,

I figured it out.
I simply needed to create single groups in the subreports that shared similar data layouts.

I then moved my cross-tabs, headers, & footers into the group's headers and footers.

This returned the result I was after.
The group filters by a database field that identifies what numerical line specified groups of testing is configured to within my LIMS database.


In short:
Now my separate groups of testing that use identical cross-tab layouts can all use one subreport vs using separate subreports that were only pointing to each group of specific testing.



Stephen