CE90WIN_EN_SP5
CE90WIN_EN_SP5
CE90WIN_EN_SP5
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>CE90WIN</strong>_<strong>EN</strong>_SP1<br />
Data Source<br />
ADAPT00098955<br />
Description:<br />
Patch ID: 34902859<br />
SQL expressions based on timestamp (datetime) in DB2 are shown incorrectly as dates instead of datetimes.<br />
New Behavior:<br />
The problem is that datetime expression fields are changed to date type in DB2. In keeping the datetime data type, the value of<br />
datetime is now shown correctly.<br />
ADAPT00122572<br />
Description:<br />
Patch ID: 34998542<br />
In Crystal Reports 9 Advanced, if a user has a JavaBeanClassPath registry setting that is more than 255 characters and they create a<br />
new report, when they try to access a JavaBean data source, the Java Beans Connectivity window does not show any Java Bean<br />
classes.<br />
When opening an existing report that is based on a JavaBean data source and the JavaBeanClassPath registry is more that 255<br />
characters, the following errors are displayed when refreshing the report data:<br />
Query Engine Error: “Failed to find the Java Class: ‘JavaClassName’”<br />
When a user clicks OK, a "Query Engine Error:" message appears.<br />
“JavaClassName” refers to the class name for the data source.<br />
New Behavior:<br />
In Crystal Reports 9 Advanced, it is now possible to successfully access a JavaBean data source when the registry setting for<br />
JavaBeanClassPath is more than 255 characters.<br />
ADAPT00126052<br />
Description:<br />
Patch ID: 35033416<br />
A "Failed to open a rowset" error is generated when attempting to open a report that has links to unknown field types.<br />
New Behavior:<br />
When loading an older report (Crystal Reports 8.5 and lower), unknown field types are now converted to string field types.<br />
ADAPT00128334<br />
Description:<br />
Patch ID: 35066692<br />
When creating a new report in Crystal Reports 9 with custom-built Btrieve/Pervasive drivers, the following error occurs when trying<br />
to access the Btrieve database table information using the Report Creation Wizard:<br />
“Btrieve [11]: Invalid filename.”<br />
New Behavior:<br />
Btrieve/Pervasive table information can now be accessed correctly with Crystal Reports 9 using custom-built Btrieve/Pervasive<br />
drivers. The "Btrieve [11]: Invalid filename" error no longer occurs when selecting Btrieve tables.
Change language