18.08.2013 Views

Service Pack Readme (Adapt)

Service Pack Readme (Adapt)

Service Pack Readme (Adapt)

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

CE10WIN_EN_SP2<br />

Object model<br />

ADAPT00307335<br />

Description:<br />

Patch ID: 36339235<br />

When users set the location on a native Oracle report in the Crystal Reports 10 Report Designer Component (RDC), the numerical fields return<br />

incorrect data. This problem only occurs in reports that were created in a previous version of Crystal Reports.<br />

The cause of problem is an incompatibility between the native Oracle database driver and reports that were created in previous versions of<br />

Crystal Reports.<br />

New Behavior:<br />

This problem is resolved.<br />

Parameters<br />

ADAPT00228208<br />

Description:<br />

Patch ID: 36141010<br />

Prompting text is not saved for the report's stored procedure parameter, for reports that are created in Crystal Reports 8.5. As a result, when a<br />

report has parameters that are based on stored procedures, the parameter name is displayed (rather than the prompting text), when the report is<br />

opened in Crystal Reports 10.0. The parameter name also appears, in place of the prompting text, when the report is viewed through a viewer in<br />

Crystal Enterprise 10.0.<br />

New Behavior:<br />

This problem has been resolved, by leaving the parameter description field blank, in the case when it is not possible to retrieve a description from<br />

the database.<br />

Known Limitations:<br />

If the database is updated directly to have an empty string as the parameter description, the Prompting Text is not set to the empty string. The<br />

user-entered value is always used.<br />

ADAPT00303119<br />

Description:<br />

Patch ID: 36289424<br />

When Crystal Enterprise 8.5 ePortfolio is used in a version 10 environment, refreshing a report in the DHTML viewer causes a looping parameter<br />

prompt.<br />

The cause of the problem is that version 8.5 of the DHTML viewer missed setting a flag. The Pageserver cannot obtain the entered parameter<br />

value; therefore, it loops continuously, in an effort to obtain the value.<br />

New Behavior:<br />

This problem is resolved.<br />

Platform .NET controls

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!