I have a Crystal 8.0 dictionary which uses a User DSN connection to a VisualFoxPro database. Some of the tables have related ID fields with mismatched datatypes. For example, the Collector_ID field in the Assets table is numeric but the Collector_ID field in the Collector table is an integer. Crystal allows me to link these tables on Collector_ID in the dictionary regardless of the difference but it barfs intermittently in the report, producing the following errors:
Error in file links
Warning: Fields in the file "collectors" cannot be linked
Dictionary integrity error
My response to this was "Duh, of course" but I am not able to make any changes to the database so I was determined to find a work around. During my efforts, I realized that the report sometimes accepts these links without error (and even produces the correct results) but other times, using the same report design and dataset, it does not. Has anyone else experienced this inconsistency? Is there a rhyme or reason to Crystal displaying results vs. errors for the same report and dataset?
Many, many thanks.
Error in file links
Warning: Fields in the file "collectors" cannot be linked
Dictionary integrity error
My response to this was "Duh, of course" but I am not able to make any changes to the database so I was determined to find a work around. During my efforts, I realized that the report sometimes accepts these links without error (and even produces the correct results) but other times, using the same report design and dataset, it does not. Has anyone else experienced this inconsistency? Is there a rhyme or reason to Crystal displaying results vs. errors for the same report and dataset?
Many, many thanks.