Hello, Wondering if someone can give me instructions on how to change my existing Crystal Reports to read our database after our conversion to MSSQL 2005 from Btrieve/Pervasive 2000i this weekend. I am running Macola version 7.6.400 and Crystal version 8.5 Developer. I know that our integrated Crystal reports won't work anymore, we never used them anyways, but I have probably 75 custom reports that I need to fix. Thanks for any advice!
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Updating Crystal Reports after Btrieve to MSSQL conversion
- Thread starter joybee36
- Start date
synapsevampire
Programmer
The method is to use Database->Set Location and point to the new table(s)
The problem may arise that you don't have a direct match, in which case you might generate Views, or rewrite part of the reports.
-k
The problem may arise that you don't have a direct match, in which case you might generate Views, or rewrite part of the reports.
-k
If your integrated crystal reports won't work anymore, you did something wrong. Are you using a reseller? Every single one of these reports converts to SQL automatically as a part of the SQL conversion.
As far as custom reports, when you created your pervasive reports, did you use the legacy ddfs or the SQL ddfs? You can tell by looking at the table names. If the tables end in _SQL, you used the SQL ddfs, in which case use database->set location as SV suggested.
If you did not use the SQL ddfs, that was a mistake in and of itself - I stopped using the legacy ddfs in 1997 for Pervasive Macola reports. The entire purpose of the SQL ddfs is to facilitate a conversion to SQL, while still being functional in a Pervasive environment.
The process to update the reports is similar, database->set location, except the table names have changed and you will have to manually set the location of each table, and in many cases the field names have changed, and you will have to manually remap the fields. So instead of this taking a minute per report it could take several minutes.
The good thing you will experience with SQL is speed. I have seen Macola reports that take 2 hours to run in a Pervasive environment that run in 6 seconds in SQL. No BS.
Please post if you have any questions.
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
"What version of URGENT!!! are you using?
As far as custom reports, when you created your pervasive reports, did you use the legacy ddfs or the SQL ddfs? You can tell by looking at the table names. If the tables end in _SQL, you used the SQL ddfs, in which case use database->set location as SV suggested.
If you did not use the SQL ddfs, that was a mistake in and of itself - I stopped using the legacy ddfs in 1997 for Pervasive Macola reports. The entire purpose of the SQL ddfs is to facilitate a conversion to SQL, while still being functional in a Pervasive environment.
The process to update the reports is similar, database->set location, except the table names have changed and you will have to manually set the location of each table, and in many cases the field names have changed, and you will have to manually remap the fields. So instead of this taking a minute per report it could take several minutes.
The good thing you will experience with SQL is speed. I have seen Macola reports that take 2 hours to run in a Pervasive environment that run in 6 seconds in SQL. No BS.
Please post if you have any questions.
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
"What version of URGENT!!! are you using?
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question