CE90WIN_EN_SP5

CE90WIN_EN_SP3
Data Source
ADAPT00253682
Description:
Patch ID: 36022963
The Crystal Reports ODBC driver does not recognize the Data Direct drivers when they are branded with different prefixes.
New Behavior:
New registry subkeys enable the ODBC driver to support other branded Data Direct drivers.
Known Limitations:
The partial driver name (the first 4 or 5 characters) must be added as a value to the corresponding string. For example, the value will
be "btor" for a custom branded driver named "btor819.dll," which must be added to the "DataDirect Oracle drivers" subkey.
ADAPT00268966
Description:
Patch ID: 36093249
When users report from an IBM DB2 database with Crystal Report's native DB2 connection, if an "or" is used in the record selection
formula, the formula fails to be processed on the DB2 server side. This problem can slow down the performance of the report
processing time.
The problem is that the "or" operator is not passed to the database.
New Behavior:
This problem is resolved.
ADAPT00296332
Description:
Patch ID: 36236582
The Crystal Reports ODBC driver does not return the correct number of characters in a CLOB memo field. This problem started in the
crdb_odbc.dll, from version 9.2.1.598 and onward.
The cause of the problem is that the column size of a CLOB field is determined by its number of bytes, rather than by its number of
characters.
New Behavior:
This problem is resolved.
ADAPT00322052
Description:
Patch ID: 36433872
When reporting off a Btrieve database with version 9.1.2.88 or greater of the crdb_p2bbtrv.dll, a memo field that is displayed on the
report will display a limit of 254 characters.
New Behavior:
This problem is resolved.
Deployment