Symptoms
When processing a report where the database connection has been overridden to point to a different database than what is saved in the report, Report Commander fails with the following error:
Cause
This problem can occur if the report uses a database command (not a table or stored procedure) as its data source, due to a problem with the Crystal Reports runtime components used by Report Commander.
This problem has only been observed with reports that connect to Oracle databases.
Resolution
To resolve this problem, disable database verification for this report as described in the following sections. If printing or exporting fails with the same error after database verification has been disabled, the problem is caused by something else.
If you are using the Command Runner (adcrutil.exe)
Add the following option to your adcrutil command line:
-verifydb-
Note that there is a hyphen before and after the option. Both are required.
If you are using the Project Runner (adrcexec.exe)
Edit the project and go to the properties panel for the affected report. On the Advanced page, change the Verify Database on Connection Override setting to "False."
Status
Beginning with Report Commander 2.1, database verification is turned off by default. Projects created using an earlier version will still have the option turned on, however.
See the download page to download the latest version.
