Crystal Reports Set Locations
Previous  Top  Next

**** Eclipse 2.4 Update - now scans the Template folder ****

This utility performs two functions:

·It scans all reports in the REPORTS & TEMPLATE folder of the active HireTrack Eclipse database, sets the the location of every table used in a report to the Eclipse DATA folder, and then saves each report. This process is only of any use to users who want to edit reports in Crystal Report and preview any changes they have made in the report designer. Although you can manually set the database location in Crystal Reports, this process its somewhat cumbersome in Crystal Report v9 onwards. Users of Crystal Reports v8.5 might also find that setting all the table locations with this tool saves them some time and tedium when editing reports.  
·Once the table locations have been correct set, this tool can Verify the Databases used by each report. This means that any changes made to the database tables due to upgrades in Eclipse will be incorporated into the reports and new fields and indexes made available when editing. Again, this is a function that you can perform in Crystal Reports itself. NOTE: sometimes changes to the structure of database index files will mean that links between tables can get broken when a report is verified and you will need to use Crystal Reports to put the links back. This is known to happen when upgrading from Eclipse 2.2 or earlier to Eclipse 2.4, but should NOT happen when upgrading from Eclipse 2.3 to Eclipse 2.4  
1. Setting Database Locations

Although Eclipse tells a report where to find its data whenever it runs from Eclipse, this has to be done manually when you are working with reports in Crystal itself. Apart from being a little tedious, this has become increasingly more complex to do in Crystal from version 8 onwards; in fact in Crystal 9 and 10 the process is very cumbersome, largely because Eclipse does not use an SQL database.

This utility will go through all of you reports and set the table locations to the correct path and save this in the report's database profile, so when you are previewing a report, Crystal will always know where to find the data.


SetLocations


2. Verifying Databases.

Once you have set all of your database locations, you can use this utility to verify that all the database defintions in a report match the current database structures in Eclipse. These database defintions in a report may get out of date with successive Eclipse database upgrades, and while this often has no impact on a report, it can sometimes cause reports to malfunction, often with an Error 534 or Error 533.

Note 1: Broken Links. When you verify the database the Crystal Engine may break/lose the links between some tables in the report. This is quite rate and will only happen if the indexes on tables have changed quite radically. You will know if any table links have been broken because although the report may not generate an error when printing from Eclipse it may be blank or missing certain data areas. In such a case you will need to manually correct the problem using Crystal's Visual Linking Expert (see your Crystal Reports manual for use). If you are not sure how unlinked tables should be linked then open up the backup copy of your report and check the table links there. Be aware that links may have also been broken in any sub-reports and these will also need re-instating.  
 
Note 2: When more than one table is linked from from a single table (e.g Crew.db and Transport.db both link from Jobs.db in the Totals subreport of the Quick Quote report) then its is sometimes very important that the Options for a link (right click on it for the menu) are set correctly. For example, in order that summary functions add up correctly, the Option "When linking to to files from this file" in older versions of the Quick Quote report need to be set to "Look up all of one, then all of the others". Check the link Options in your backup copy of your report to verify this.