We currently have a Visual Basic application into which we've imported a number of Crystal 8.5 Reports (as DSRs using CRViewer), in order to make them part of the VB executable (thereby eliminating the need for Crystal Reports being installed on the user workstation).
The problem is that these reports' locations are all pointing to the Development environment's SQL Server. To promote the VB app to QA, then to Production, we have to re-point the reports to the QA, then Production, SQL Servers, respectively. The only way we have to do this is to re-open the Visual Basic application and (re)Set Location on each of the Crystal reports now residing within the VB app. This compromises the proper method of promotion, which is to promote the application components to each new level (QA, then Production) WITHOUT modification.
How can we do this without having to modify and rebuild the VB app at each promotion level? I understand that there is a third-party product called Object Manager, from APS Systems, Inc., but APOS' documentation doesn't mention whether it will work with the VB-based components.
The problem is that these reports' locations are all pointing to the Development environment's SQL Server. To promote the VB app to QA, then to Production, we have to re-point the reports to the QA, then Production, SQL Servers, respectively. The only way we have to do this is to re-open the Visual Basic application and (re)Set Location on each of the Crystal reports now residing within the VB app. This compromises the proper method of promotion, which is to promote the application components to each new level (QA, then Production) WITHOUT modification.
How can we do this without having to modify and rebuild the VB app at each promotion level? I understand that there is a third-party product called Object Manager, from APS Systems, Inc., but APOS' documentation doesn't mention whether it will work with the VB-based components.