Hi all,
I am using CR 8.5. I have a report that I set to a particular database while using CR. In a VB6 app I have a form with the Crystal Reports Control. The report will run fine given the database is the same.
I am sharing the development of the application with someone at another location. I am trying to figure out how, in VB, to override the embedded (for lack of a better word) database info in the CR report itself. In other words, by changing one or more constants in our code, can we get the report to point to our respective local database when we individually run it.
I see the CR control on the VB form has a number of properties, such as .Connect and .Datasource that seem like I could use these to change the database connection. I was unsuccessful using the .Connect property by itself. It did not overwrite the database pointer in the report. So any examples of VB code to get this done would be great.
This is already how we change which SQL Server we each use. We each have a Global Const in a seperate module that contains our connection string. Our respective connections differ, but since only the const is referenced elsewhere in the code when establishing an ADO connection, every works fine. Now, if we could just get the same approach working for the report that would be great.
Thanks!
I am using CR 8.5. I have a report that I set to a particular database while using CR. In a VB6 app I have a form with the Crystal Reports Control. The report will run fine given the database is the same.
I am sharing the development of the application with someone at another location. I am trying to figure out how, in VB, to override the embedded (for lack of a better word) database info in the CR report itself. In other words, by changing one or more constants in our code, can we get the report to point to our respective local database when we individually run it.
I see the CR control on the VB form has a number of properties, such as .Connect and .Datasource that seem like I could use these to change the database connection. I was unsuccessful using the .Connect property by itself. It did not overwrite the database pointer in the report. So any examples of VB code to get this done would be great.
This is already how we change which SQL Server we each use. We each have a Global Const in a seperate module that contains our connection string. Our respective connections differ, but since only the const is referenced elsewhere in the code when establishing an ADO connection, every works fine. Now, if we could just get the same approach working for the report that would be great.
Thanks!