Crystal Reports DataSource Location still wrong even after setting the right Connection

[nouramayre]

Hey Everyone, 
i edited some Layouts for A Customer in the Workshop DB. 
After Layouts where finilized i saved them as a rpt. and imported them to the Productive DB.
Preview in SAP Works perfectly!
But Preview in CR does not work at all due to wrong Connection althoug i set it to the Productive Database.
Screenshots of the Query show that connection it still divided between 2 Databases. 

thanks in Advance 

[JWiseman]

That could be the problem...i.e. the OADM & OADP tables being brought in without any links to the other tables.

Sticking with the method of unlinked tables assuming that it was working for you (generally not supported) you can also try this: Make a test copy of your report and in the test copy link the two tables in question. Now set the DB Location. Afterwards unlink the two tables like you had before.

There are a couple of alternatives to get that data into your report if the above doesn't work and you can't link them as dimensional tables.  Make sure that you do a Save As so that you have at least one backup copy before you remove those tables from the main report's DB explorer.

1. Use a SQL Expression for each of the fields that you need in your main report.
2. Create one Report Header level Subreport for each of the two tables and bring in the required values via Shared Variables. This is probably the easiest way.

[JWiseman]

Sticking with the method of unlinked tables assuming that it was working for you (generally not supported) you can also try this: Make a test copy of your report and in the test copy link the two tables in question. Now set the DB Location. Afterwards unlink the two tables like you had before.

[nouramayre]

@JWiseman you mean this 

[JWiseman]

Hey nouramayre, can you post a pic of the Database Expert > Links dialogue? I'm guessing you're using B1 based on the naming convention...I haven't used B1 in a very long time but it looks like the report has unlinked tables and / or procs in the main report...this can cause problems (and isn't supported) and thus may be the issue.