More Crystal Reports nonsense

[Daspoo]

Ok, heres the $50,000 question: Has anyone experienced attempting to export a Crystal Report - created outside of the VS.NET environment - that is based on a stored procedure that accepts 0 parameters? I have a situation in which a report needs to be based on a stored proc. in order to quickly manipulate data to return to the user. However, since the report is so generic in its use and data, the stored proc requires no parameters.

Everytime I attempt to export this silly report, I receive an error stating:
==========================================
Error in File <myFile.rpt>: Error detected by export DLL:
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: CrystalDecisions.CrystalReports.Engine.ExportException: Error in File <myFile.rpt>: Error detected by export DLL:
==========================================
The error occurs on the line:
"RptDocument.export( )"

Anyone had the same experience? Any ideas as to how to resolve this? Thanks in advance.

 

[rustyd]

I use Crystal Reports 7 with a VB5 app and my users experienced similar issues when they tried to export the report themselves to the various other file types from the preview window. In order to export (explicitly called from the code or user attempt from preview window) the appropriate files must be installed on their machine. Works fine in the development environment.

There is multiple (10+ easy) additional files to export to the typical export formats (text file, excel spreadsheet, html, email, etc...). The crystal decisions web site lists all of the files needed to export to particular files. Hope this helps.