I'm using VB6 with CRXI and an SQL Server database. I pass the OLEDB DSN and database name dynamically through the VB code. This has worked fine.
I've recently added a dynamic parameter to an existing report. When I try to run the report from my VB app and pass the new DSN and database, I receive a "Failure to load Values..., Vendor Code 17" which is a database connection error. But this error ONLY pertains to the dynamic parameter. If I set the parameter to static - the report runs correctly.
I am familiar with the Vendor 17 error message because I used to receive it on the main report when trying to pass the DSN and Database through code. I removed the value in the "Overriden Qualified Table Name" in the table Properties List under the "Set Datasource Location" and then could pass the DSN and Database name without errors.
My question... Is there a similar setting in Crystal Reports for dynamic parameters that I can change to allow VB to pass a DSN and database name to the parameter value at runtime?
I've recently added a dynamic parameter to an existing report. When I try to run the report from my VB app and pass the new DSN and database, I receive a "Failure to load Values..., Vendor Code 17" which is a database connection error. But this error ONLY pertains to the dynamic parameter. If I set the parameter to static - the report runs correctly.
I am familiar with the Vendor 17 error message because I used to receive it on the main report when trying to pass the DSN and Database through code. I removed the value in the "Overriden Qualified Table Name" in the table Properties List under the "Set Datasource Location" and then could pass the DSN and Database name without errors.
My question... Is there a similar setting in Crystal Reports for dynamic parameters that I can change to allow VB to pass a DSN and database name to the parameter value at runtime?