How do I avoid having a newly linked table use an explict database name?

Question

Greetings!
I am using Crystal Reports XI (version 11.0.0.895).
I had to add a new field from a new table to a report.  The original report was based on an ODBC connection named "WinCaps".  On my machine, that connection is associated with a database named "AK 94 4_15".  I added the table and the link (a left outer join) and ran it on my machine.  It worked.  I uploaded it to the customer's machine.  The customer also has an ODBC connection named WinCaps, but on his machine, it's associated with a database named "Anneal".  I tried the report.  It failed.  I went back to my machine and looked at the database query from my test.  It was:
SELECT "alarm_history"."alarm_date", "alarm_history"."message", "alarm_history"."state", "alarm_history"."charge", "alarm_history"."ack_date", "alarm_history_ext"."recorded_time"
FROM   {oj "public"."alarm_history" "alarm_history" LEFT OUTER JOIN "AK 94 4_15"."public"."alarm_history_ext" "alarm_history_ext" ON "alarm_history"."alarm_pkey"="alarm_history_ext"."alarm_fkey"}
WHERE  "alarm_history"."charge"=4584
Note the explicit database name of the table after "LEFT OUTER JOIN".  Where did that come from and how can I get rid of it?  I cannot have it in there because we frequently need to test our system against a copy of a customer's production database, and to do that, we change the database associated with the "WinCaps" DSN.  The report needs to work whether the database behind the WinCaps DSN is "Anneal", "AK 94 4_15", or any other name, as long as the schema is the same.
Thank you very much!
RobR
Edited by: Radcon Entec on Apr 20, 2009 4:06 PM

Answer 1

Richardson's Second Law of Computational Unpredictability states:
"The word 'should' has no meaning".
Despite the fact that there should be no difference, the fact remains that the difference remains and it is very significant and troubling. 
In the past, I have tried going into the Database Expert and selecting an OLEDB connection instead of an ODBC connection.  I have never succeeded in doing that.  The dialog box that first appears asks for a user name and password.  I enter a user name (for example, "MyUser") and a password.  I then fill in anything else that looks reasonable, save the report, and try to open it.  I get an error message saying "Database MyUser does not exist".  No kidding.  MyUser is a user name, not a database name.  It appears that the OLEDB dialog box is not set up correctly.  If you are suggesting using that connection, please provide step-by-step instructions on how to do it.  If that is not what you are suggesting, please explain how to use the Microsoft OleDB Driver for ODBC when setting up a report.
Thank you very much.
Rob Richardson