I'm using Crystal Reports 2008, CR Developer 12.2.0.290. The data I'm access is in a SQL Server 2000 database. I'm using on ODBC connection.
I've created an absolute performance pig of a report due to the functionality demanded by the users throughout the company. It is a job docket that encompasses all the various aspects of our production. The report is set up to suppress any sections that are not required for each particular job. It has 33 subreports (I know, I know). Each of the subreports relate to one aspect of the production process and are supressed if no data is entered into that table (or that section of the table since some of them share tables). They are also laid out in the order that production has specified (although I may discuss that with them if there are performance gains to be realized by rearranging things).
I'm trying to attach it here for you to take a look at it, if you wouldn't mind. It runs fine on new computers, but the old clunkers we have in our production areas are bogging down trying to pull up the docket information.
Any suggestions for improving its performance would be greatly appreciated.
I've created an absolute performance pig of a report due to the functionality demanded by the users throughout the company. It is a job docket that encompasses all the various aspects of our production. The report is set up to suppress any sections that are not required for each particular job. It has 33 subreports (I know, I know). Each of the subreports relate to one aspect of the production process and are supressed if no data is entered into that table (or that section of the table since some of them share tables). They are also laid out in the order that production has specified (although I may discuss that with them if there are performance gains to be realized by rearranging things).
I'm trying to attach it here for you to take a look at it, if you wouldn't mind. It runs fine on new computers, but the old clunkers we have in our production areas are bogging down trying to pull up the docket information.
Any suggestions for improving its performance would be greatly appreciated.