Do consider Dell's suggestions. One thing that has me wondering though is; if the report prints fine, but "crashes" when sent to the viewer, then variables like database client, printer drivers, etc., should be fine... maybe...
I think a bit more of a description of "crash" will be good; Error? Actual behavior? Etc.
Enabling the "Verify on 1st refresh" options will not be a bad idea for now.
Check to see if the report has "saved data". If it does, disable this option.
A really simple new app using a saved data report may be a good test - pointing us in some direction. My preference would be a one liner;
CrystalReportViewer1.ReportSource = <path to saved data report>
Understanding the pressures of the business case, let's take today and tomorrow to see if we can resolve the issue here. If not, you may want to consider creating a phone incident next week(?). Phone incidents can be created here:
Crystal Single Case Technical Support - SAP Business Objects US Online Store | SAP Online Store
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter
