A client recently upgraded to version 2013 service pack 3 (from version 4.5).everything in Sage100 is good; however, when they run Crystal Reports they have something odd that I have never seen and apparently neither has Sage. Here is what is going on:
User previews a Custom Crystal report from the Sage 100 ERP custom reports menu. The report has STATIC parameters. User specifies parameters and report generates. Then, when the user attempts to export as PDF, they get re-prompted for the parameters, and the report does not export correctly. LOOKS like the report created the PDF, but when they try to open it, they get an error message indicating that the report is corrupted.
This process worked fine in version 4.5.
Anyone out there seen this?