Set Datasource Location does not update properly on Crystal Subreports

[Former Member]

Greetings -

I have a customer who is having great difficulty switching between Development, Test, and Produstion database environments in Crystal (version 10.0.0.533). FYI, Connecting via ODBC to SQL Server databases.

When using the Set Datasource Location option to switch databases (e.g. from Test to Development), the updates do not always propogate to the subreports. Some subreports will continue to point to the original database (e.g. Test) instead of the new database (e.g. Development).

It's very frustrating for us!  We use the Set Datasource Location for Crystal Reports design and testing.

Anyone see this before?  Any ideas on how to fix or workaround it?

Thank you,

Eric Kenney

[abhilash_kumar · Accepted solution]

Hi Eric,

When you do a 'set datasource location', make sure you select each table from the original datasource and the new datasource and then hit the update button.

Trying to change the datasource by clicking on the connection names doesn't really work well.

In case of subreports too, make sure you update each table as opposed to just updating the connection.

Hope this helps!

-Abhilash

[Former Member · Accepted solution]

Hi Abhilash,

Yes, we do hit the update button on each of the tables.  The problem is: this works most of the time, but not all of the time.

We do have a workaround, which is to point to a copy of our database structure stored in Access via ODBC, then repoint to the other SQL database environment via ODBC.  That works about 99% of the time.

Questions:

1. Do you know of any plans to address this issue by Crystal in a service pack or future version?

2. Do you know of any other solution or workaround to this issue?

Thank you for all your help,

Eric Kenney

[abhilash_kumar · Accepted solution]

Hi Eric,

I'm not sure if this is because of the CR version you're using. I use CR 2008 SP3 FP 3.6 and this method works 100% of the times.

To be honest, updating by clicking on the table names is the only way this is supposed to work.

Why don't you download CR 2008 or CR 2011 and evaluate the product for 30 days, perhaps that might answer if this is due to the version?

-Abhilash

[Former Member · Accepted solution]

Thanks again, Abhilash.  We'll give that a try a let you know.

Eric

[former_member1236711 · Accepted solution]

Works like charm.!

[pgenga]

I am facing a similar challenge..

Though I have used it many times this time I am changing from MySQL ODBC to XSD file and it is not doing anything though it comes up button enabled CRforVS2019 VS 30 please advice