Posted on 2006-06-09
I have a report I developed with Crystal. It is using a stored procedure from our development server and test db.
The production server is physically a different machine, geographically not at our office, and the db name is slightly different as well.
My question is: Is there a reliable way to change the server, and db from code (during runtime) so once we go live with some reports, they will still work on the other server machine with the other db?
I Crystal article I came accross, says: "...When using the SetDatabaseLogon() method, the report must connect to the same server and database with which it was designed...." <-- IS THIS CORRECT???
It can't be that I have to develop the report against the final server and db right from the beginning!
Am I missing something here? Is there another approach?
Also, What do I do about the stored procedure(s) that the report is using? do they need to get "re-pointed" as well?
Our delivery is 6/14/2006 - and I only found this out now!