Crystal Reports 9 over network: slow initialization

Question

We have a VC++ application that uses Crystal Reports RDC (actually 8.5, and trying to change to 9.2). By design our application is installed on a file server and users execute it directly from the server, without copying or install any component in the local drive. We just register the minumum Crystal Reports DLLs needed to point directly to the location of this DLLs in the server. So we don't copy any Crystal Reports Runtime DLLs to c:\
At this time, with Crystal Reports 8.5, the minimum runtime DLLs on the server needed to run our application and print reports have a size of 8Mb, and the first time our application tries to open a report it hangs for about 5 seconds (with FileMon I see that Crystal Reports is loading its runtime DLLs). But now I'm trying to change it to use Crystal Reports 9 (due to unsolved CR8.5 limitations). With this version our minimum required runtime DLLs have a size of almost 12Mb, and the load time of this DLLs become almost 10 seconds (too big).
I did tests with Crystal Reports XI and it was even worse. If I copy and register the DLLs in the local drive it loads very fast, but we need to make it to work directly from the server without copying the files to c:\
Is there any way to reduce the loading time of this runtime DLLs without having to copy them to the local drive? Thanks

Answer 1

Well, I think the problem you had with CR XI is that you can not just copy the dlls. You have to use the merge modules and create a deployment project using a utility such as InstallShield, Wise, MS Visual Installer, etc.
As far as the issue at hand.
Here is a basic list of possible issues that may improve the performance:
Report Design Issues
u2022     Linked OLE object inserted into a report is not where the report expects it to be. If this is the case, the report will attempt to locate the object, potentially consuming large amounts of time.
u2022     The subreport option "Re-import when opening" is enabled (right click the subreport(s), choose format subreport, look at the subreport tab). While this is a great design time feature, it is a time consuming process and should be used judiciously.
u2022     Specific printer is set for the report and the printer does not exist. Try the "No printer" option (File | Page setup).
u2022     Also, see the Article u201CHow Printer Driver Options Affect a Reportu201D regarding printers and Crystal Reports;
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a09051e9-721e-2b10-11b6-f9c65c64ef29
u2022     The number of subreports the report contains and in which section the subreports are located will impact report performance. Minimize the number of subreports used, or avoid using subreports if possible. Subreports are reports within a report, and if there is a subreport in a detail section, the subreport will run as many times as there are records, leading to long report processing times. Incorrect use of subreports is often the biggest factor why a report takes a long time to process.
u2022     Use of "Page N of M", or "TotalPageCount" special fields. When the special field "Page N of M" or "TotalPageCount" is used on a report, it will have to generate each page of the report before it displays the first page. This will cause the report to take more time to display the first page of the report
u2022     Graphics, while a powerful feature of Crystal Reports, need to be used with care. When displaying a report using the Web Forms report viewer, for each chart or image on the report page, the report engine must create a temporary JPG file and the browser must make a separate request to the web server to retrieve it. The Web Forms viewer also periodically searches through the images folder for old images and deletes them. This disk access and creation of temporary files will reduce report performance.
u2022     Remove any unused object from the report. This includes database tables, formulas and parameters and running total formulas. Even if these objects are not used in a report, the report engine will attempt to evaluate the objects, thus affecting performance.
u2022     Suppress unnecessary report sections. Even if a report section is not used, the report engine will attempt to evaluate the section, thus affecting performance.
u2022     If summaries are used in the report, use conditional formulas instead of running totals when ever possible.
u2022     Whenever possible, limit records through Record selection Formula, not suppression.
u2022     Use SQL expressions to convert fields to be used in record selection instead of using formula functions. Since SQL Expression Fields are added to the SELECT clause of the SQL Query the SQL expressions are evaluated server side.
For example, if you need to concatenate 2 fields together, instead of using a formula, create a SQL Expression Field.
u2022     Using one command table or Stored Procedure or a Table View as the datasource can be faster if you returns only the desired data set.
u2022     Perform grouping on the database server. This applies if you only need to return the summary to your report but not the details. It will be faster as less data will be returned to the reports.
Report Options
u2022     u201CVerify on First Refreshu201D option (File | Report Options). This option forces the report to verify that no structural changes were made to the database. There may be instance when this is necessary, but once again, the option should be used only if really needed. Often, disabling this option will improve report performance significantly.
u2022     u201CVerify Stored Procedure on First Refreshu201D option (File | Report Options). Essentially the same function as above, however this option will only verify stored procedures.
If the above does not help, perhaps that is the best performance you will get over the network and going to a web based solution may be worth considering(?). Let's see if anyone else can provide any help.
Ludek