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 />
ADAPT00142114<br />
Description:<br />
Patch ID: 35179010<br />
When a user publishes a report that is based on a native Sybase connection to Crystal Enterprise, the value for decimal places in<br />
Numeric type data fields is reset to 0.<br />
New Behavior:<br />
New registry subkeys have been provided to enable users to set a value that ensures decimal places in Numeric type data fields are<br />
retained. In Crystal Reports 8.5, the registry subkey is in the following locations:<br />
HKCU\Software\Seagate Software\Crystal Reports\DatabaseOptions\SYBASE and<br />
HKLM\Software\Seagate Software\Crystal Reports\DatabaseOptions\SYBASE.<br />
In Crystal Reports 9, the subkeys are in the following locations:<br />
HKCU\Software\Crystal Decisions\9.0\Crystal Reports\Database\SYBASE and<br />
HKLM\Software\Crystal Decisions\9.0\Crystal Reports\Database\SYBASE<br />
The key is a string value, "OverrideNumericConversion". Set it to "Yes" to ensure that the decimal places are kept. The default value is<br />
"No."<br />
ADAPT00145238<br />
Description:<br />
Patch ID: 35193657<br />
When running a report against a proprietary database via ODBC in Crystal Reports 9, the SQL statement issued to the database was<br />
different from the SQL statement that would have been issued from Crystal Reports 8.5. This generated consistency problems between<br />
the way the report worked between Crystal Reports 8.5 and 9.<br />
New Behavior:<br />
The ODBC connectivity has been adjusted to allow for the same behavior in this scenario in Crystal Reports 9 as found in Crystal<br />
Reports 8.5.<br />
ADAPT00147477<br />
Description:<br />
Patch ID: 35203270<br />
The time portion of a DateTime field does not show up in a report when using the Borland Database Engine.<br />
New Behavior:<br />
The time portion should now show up correctly in a report that uses the Borland Database Engine (either using Database Files or<br />
IDAPI Database DLL to make the connection).<br />
ADAPT00148810<br />
Description:<br />
Patch ID: 35209798<br />
When you use a custom PC database driver, and select a table to report from, the errors "Failed to open a rowset" and "Not<br />
Implemented" appear.<br />
New Behavior:<br />
The system can now process tables from any custom PC database driver.
Change language