| Home | RDP Sales | Contact Us | Training |
|
| RDP Support | ||||
|
RDPWin Knowledge Base |
RDP-DOS Knowledge Base |
IRM and IRM.Net Knowledge Base |
Crystal Knowledge Base |
|
Some Crystal Reports were loading very slowly in both RDPWin and in the Crystal Designer. The problem usually only manifests itself when there are subreports in the report. The more subreports, the longer the load time. The owner statement report was taking almost a minute to load.
The real problem is that Crystal Reports use the printer driver to format the report. This printer driver is stored as part of the report. Some printer drivers cause the formatting to take a long time. By defining "No Printer" as part of the main report and ALL subreports, a generic driver is used, which is much faster for formatting. This does not effect the format of the report, when it is finally printed since the driver for the printer chosen at this time is used. With the owner statement reconfigured, it now takes less than a second to load.
Subreports that are an external file have one copy on the disk in the report file and another copy in the main report. The two subreports are not the same. If changes are made to the external file, the copy in the main report is not changed. The subreport must be re-imported in order to get the new changes. So, all the subreport external files must be changed to No Printer and then re-imported into the main report. The steps below outline this procedure.
Reports that don't have and subreports seem to load quickly with or without the "No Printer" being checked, so changing those reports is optional. All RDP standard Crystal Reports will be changed to the "No Printer" setting.
Main Report:
Modify All Subreports:
Continue with Main Report:
| Home | RDPWin | RDP-DOS | IRM/IRM.Net | Open A Web Support Ticket |
|---|---|---|---|---|
|
Version 2.xxx | Upgrade to RDPWin | Link to Marketing Site | Contact Us |
| Training | Vendor Interfaces | Troubleshooting | RDP Sales Website |