Our company's application has 18 Crystal Reports which access a SQL Server database using the OLE DB driver. However, one of these reports is not working correctly when the program is installed at the user's site.
Normally when these reports are created, CR stores the reference to the local server and database in the report. Of course, once the application is deployed at the user's site, the report should access the new server and database. One of our reports consistently fails to be able to do this. My supervisor says that his previous developer found a way to enable the 17 reports to be easily "relocatable", you might call it. But how this was done has been lost. My supervisor says he believes it was done by causing the report not to store the server and database names.
Our application is using the RDC ActiveX components in Delphi. Before opening the report, the application makes a call to SetLogOnInfo for each table in the report to be updated to the local server and database. Our 17 reports work correctly this way, but I have discovered by experiment that a report created from scratch does not work; it does not seem to respond to being "relocated" in this way. I also tried modifying one of the working reports by adding a new table to it, adding new fields, removing the old fields, and finally the old table. This also failed to be relocatable.
Is there some "treatment" that needs to be applied to a report that allows it to change at runtime from one database to another? Is this something that can be done programmatically at runtime, or is it done statically at report creation time? Any help with this question would be greatly appreciated.
Patrick Manion
Normally when these reports are created, CR stores the reference to the local server and database in the report. Of course, once the application is deployed at the user's site, the report should access the new server and database. One of our reports consistently fails to be able to do this. My supervisor says that his previous developer found a way to enable the 17 reports to be easily "relocatable", you might call it. But how this was done has been lost. My supervisor says he believes it was done by causing the report not to store the server and database names.
Our application is using the RDC ActiveX components in Delphi. Before opening the report, the application makes a call to SetLogOnInfo for each table in the report to be updated to the local server and database. Our 17 reports work correctly this way, but I have discovered by experiment that a report created from scratch does not work; it does not seem to respond to being "relocated" in this way. I also tried modifying one of the working reports by adding a new table to it, adding new fields, removing the old fields, and finally the old table. This also failed to be relocatable.
Is there some "treatment" that needs to be applied to a report that allows it to change at runtime from one database to another? Is this something that can be done programmatically at runtime, or is it done statically at report creation time? Any help with this question would be greatly appreciated.
Patrick Manion