Article

EXPORT method of Crystal Reports ActiveX Automation object fails with error 5890

« Go Back

Information

 
Article Number000059917
EnvironmentProduct: Progress
Version: 8.3E, 9.1D, 9.1E
Product: OpenEdge
Version: 10.x, 11.x
OS: Windows
Other: Crystal Reports 9 / 10 / XI / XI R2
Question/Problem Description
EXPORT method of Crystal Reports ActiveX Automation object fails with error 5890.

Trying to export a Crystal report to a file or other location. 

Error 5890 occurs when calling the EXPORT method.

Error varies slightly depending on the version of Crystal that is in use.

Using the LogOnServer method to establish the initial connection to the database for the report.

Parameter values used in the LogOnServer method (specifically the ODBC DSN) differ from those used when the report was created.
Steps to Reproduce
Clarifying Information
Using the COM Report Designer Component (RDC).
Error MessageError occurred while accessing component property/method: EXPORT.
Logon failed.
Error code: 0x80020009 (5890)

Error occurred while accessing component property/method: EXPORT.
Failed to open the connection.
Error code: 0x80020009 (5890)
Defect/Enhancement Number
Cause
The EXPORT method of the Crystal RDC needs to establish a connection but fails because the ConnectionProperties saved in the report are different from those supplied in the LogOnServer method. The EXPORT method fails to override these properties and therefore cannot connect causing the error.
 
Resolution
Programmatically override the ConnectionProperties stored in the Crystal report.

Option #1
Completely override the ConnectionProperties collection stored in the report and replace it with a Connection String. This method would remove the need to setup an ODBC DSN.
Refer to article 000011041, "How to use a DSN-less connection with the Crystal Reports ActiveX Automation components in ABL" for more information.

Option #2
Use the ConnectionProperties collection to override the properties stored in the report, replacing saved values with new ones.
Refer to Option #1 in solution 000021094, "How to display a Crystal report via 4GL using the Crystal Report Viewer ActiveX Control" for more information.

Option #3
Override the DSN property stored in the report only and continue to use the LogOnServer method.
Refer to solution 000020800, "Crystal Reports: How to change the ODBC DSN connection at runtime?" for more information.
Workaround
Notes
Attachment 
Last Modified Date4/9/2015 3:06 PM
Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.



Feedback
 
Was this article helpful?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025