18.08.2013 Views

CE10WIN_EN_SP6

CE10WIN_EN_SP6

CE10WIN_EN_SP6

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.

<strong>CE10WIN</strong>_<strong>EN</strong>_SP4<br />

CRW designer<br />

ADAPT00478652 Patch ID: 37836103<br />

Description:<br />

The Informix datetime column types Year to Second, Year to Minute, Year to Hour, Year to Day, Year to Month, and Year to Year are<br />

handled as strings by Crystal Reports.<br />

New Behavior:<br />

Crystal Reports handles Informix datetime column types as datetime entities.<br />

Crystal Report<br />

ADAPT00390468 Patch ID: 37305306<br />

Description:<br />

The number format for negative numbers fails to be displayed properly when reports are exported to Excel and viewed on a machine<br />

with regional settings that are set to languages other than English (United States).<br />

The cause of the problem is that the built-in cell format strings that are used by MS-Excel are different across languages.<br />

New Behavior:<br />

The problem is resolved by not using the format strings that are used by Excel.<br />

CSP Eportfolio<br />

ADAPT00357566 Patch ID: 36962374<br />

Description:<br />

A dialog box that warns users they are about to view non-secure content appears when users log on to InfoView version 11 or to<br />

Viewing Discussions for version 10. This problem occurs on Windows systems that have Secure Socket Layers switched on. Clicking<br />

Yes or No on the dialog box has no consequence and the page is displayed.<br />

New Behavior:<br />

This problem is resolved.<br />

Data Source<br />

ADAPT00433476 Patch ID: 37496640<br />

Description:<br />

Crystal Reports displays an error message when creating a JNI Javabean report that requires a parameter with the IBM JVM.dll.<br />

The cause of the problem is the particular API call that the driver uses when the return type of the method is boolean.<br />

New Behavior:<br />

To fix the problem, the driver uses a different API call.

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

Saved successfully!

Ooh no, something went wrong!