I have reporting application created in Borland C++ Builder 6 that uses the Crystal Reports VCL component to generate reports that use a SQL Server 2000 database. We have installed our system into numerous sites and over time scripts are created to make changes to the database and change the DB Version. Most of our sites are all running different DB Versions. We have a sample DB (that is the latest version) that we use to create and and test our new reports or report changes against.
How quite often when we release a new report or report change to a client after testing it against our database we getting an error when running the report stating:
"Failed to open rowset."
We can normally fix this error by opening up the report file in Crystal Reports, Adjusting some settings in the Set Datasource option, Validating the report and saving. However even sometimes following this same procedure fails and we have to find other workarounds.
My question is does anyone know of a better way to safe guard against getting this error?
NOTE: A few reports do use 2 different DB to get the data (but the above issues isn't restircted to thsoe reports) and in these reports we set the individual Table Connection properties at runtime. We also do use a few different DB Users for accessing data from the DB.
Thanks and if you require any more information please let me know.