Examples:
Reason:
This can happen if you use SELECT * FROM ... In a Command inside the Crystal Report and you at the same time create it on a database that is not the final database (example: you make it against a test system and then move it over to a live system)
If these two databases then do not have the same UDFs a definition of those will be inside the Crystal Report (because SELECT * also include UDFs) and the Report will fail to run on the target system as it have different UDFs
How to Fix:
There are 3 options (We recommend the first as it will also give better performance and 3rd is B1UP specific)
Option 1:
Replace the SELECT * with the fields you are actually using in the Crystal Report. An example on how to do that can be seen here
Option 2:
In the Crystal Report Design on the Customers system or against a real copy of the right system. Open the Crystal Report and choose Database > Verify Database
This will force the system to update what UDFs are in the Crystal
Option 3 (B1UP Only - Not recommended unless option 1 or 2 is impossible):
- Go to Administration > Add-ons > B1 Usability Package > B1 Usability Config
- On the Options Tab turn off the feature "Do not perform a 'Verify Database' on report load"
- Press update
(The reason we do not recommend this option is because it doubles the time it takes to display a Report)
Comments
0 comments
Please sign in to leave a comment.