Hey Mitch,
So this is a Crystal error and diagnosing it can be a pain in the rear sometimes. This isn't ideal, but sometimes the best way to diagnose it is to load up the full copy of Crystal where you are trying to run the report via Logicity and get more verbose steps on what is going on. Knowing how painful that might be, here are a few common problems:
- The ODBC connection for your reports (if you use them) need to be set up under the 32-bit ODBC control panel.
- When you 'Set Location' on a report it stores a bunch of details about the connection at the time the designer wrote it - including the server name, user name the DESIGNER connected as, database name, etc. If any of that doesn't align perfectly with your deployment you can get this error.
Hope some of this helps!
Adam