Changing databases without touching the RPT
Posted on 2002-04-23
I have developed several Reports (RPTs) that connect to a development SQL Server 2000 database using OLE DB.
Now that they have been completed they are going to be submitted to a source code control system (probably Visual Source Safe) and migrated into testing and then one day into Production.
Each time they are migrated they will be using a different database however technically I shouldn't be touching the insides of an RPT file as it moves through these stages. Any modifications should occur in the development stage and cause new versions of the file to be generated and then controlled.
So, I would like to be able to change the database an RPT is linked to without changing the RPT file.
One idea I had was to link the RPT to a local UDL file. Then all I would have to do is change the UDL file when I change databases. It seems though that the Report Designer only uses UDL files to extract connection info and then stored the info in the RPT file afterall.
I took a look at Crystal Queries but they only use ODBC.
I do not want to use ODBC DSNs as the solution I want to stick with OLE DB because then nothing has to be configured on the PC.
I also hope to install these reports in Crystal Enterprise. Can I specify the database they are to use when they are installed into Crystal Enterprise? This may solve my problem too.