Symptoms
Report Commander fails to export a report, giving one of the following error messages:
Cause
This error is returned by the Crystal Reports engine under many different circumstances, and is misleading because it generally does not involve a file path.
Missing or mismatched database driver
The error is reported when the required database driver is not installed, or when you are running the 64-bit version of Report Commander but only the 32-bit version of the driver is installed, or vice versa. This has been observed with Oracle and KB_SQL drivers.
Be sure the correct driver (32- or 64-bit) is installed for the Report Commander version you have installed.
On 64-bit platforms you can choose either the 64-bit version of Report Commander (requires 64-bit drivers) or the 32-bit version (requires 32-bit drivers). See the download page for more information.
Missing ODBC alias
The error is reported when an ODBC alias used by the report is missing. If this is the cause, you will often see a previous warning message indicating that "Database connectivity test failed" for one or more tables in the report.
Be sure the ODBC alias is configured correctly. The name of the alias must match the data source name in the report.
If you are running the 32-bit version of Report Commander on a 64-bit computer, the alias must be defined using the 32-bit ODBC Data Source Administrator, not the regular ODBC Administrator.
If the report works correctly for one user but fails for others, be sure that the ODBC alias has been created as a System DSN or that it has been created for all users who need to execute the report.
Missing table or field in report
The error is reported when the report uses a table or field that is missing from the data source. If you are getting this error, open your report in the Crystal Reports designer and make sure it is connected to the same database you are trying to use with Report Commander. Then use the Database > Verify Database command (in Crystal Reports) to verify the database. If any errors are reported, confirm that your report still works as expected. Then save it and test Report Commander again against the updated version.
