Guest_imported
New member
- Jan 1, 1970
- 0
I've recently tried to automate native connection using VB6 to open a crystal report and change the database logon and set the locations to the client server so that the reports don't have to be setup for the client manually.
However, it appears that the report doesn't forget the original location of the database and no matter what point I try to change the table locations and server logon I get an error before the report comes up 'Unable to open SQL Server'. Therefore, I still had to setup the reports manually for the client. Is there anyway you can pass in code, native connection to reports or do I have to go back to creating a fixed ODBC connection and use that.
However, it appears that the report doesn't forget the original location of the database and no matter what point I try to change the table locations and server logon I get an error before the report comes up 'Unable to open SQL Server'. Therefore, I still had to setup the reports manually for the client. Is there anyway you can pass in code, native connection to reports or do I have to go back to creating a fixed ODBC connection and use that.