Crystal Reports upgrade gotchas

(1) Share

Report

Posted on by Bruce.T

405

Hi,

While testing our SL7 to SL2015CU2 upgrade we have noted a number of Crystal report issues (see below). As Crystal 2008 used in SL2015 is several versions old we have not been able to find any documentation of the differences or gotchas we will need to resolve. Does anyone have anything they can share?

Some of the changes/issues we have encountered are

- Numbers must now be passed without delimiters ie 9 not '9'

- Dates must be delimited with # eg #31/01/2017#

- {} required around database fields

We are also trying to better understand why we get this error when the dates are at the beginning of the select parameters but if we move these to the end the error does not occur.

Any help/guidance would be appreciated.

*This post is locked for comments

All responses (1)

Answers (0)

David Callery 1,135 on at

Like (0)

Report

RE: Crystal Reports upgrade gotchas

Don't know if this helps but I have upgraded to CU2 which has compromised some reports. I have some custom reports using views that were running fine in SL2015 CU1 and when the update of CU2 was applied, the templates for selecting some parameters did not work. When I looked at the report, all appeared fine but when I looked at the source view in Crystal, all of the data properties were set to "string" Looking at the original view in the database, those properties are correct as Integer, Date, etc.

In my investigation, this is noted as a Crystal issue and the only way I have gotten around it was to redo the report.