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>_SP2<br />
ADAPT00213391<br />
Description:<br />
Patch ID: 35828580<br />
The Java Bean database driver cannot reliably display string fields. The Report Designer crashes if a string field length goes over 276<br />
characters.<br />
New Behavior:<br />
The driver has been fixed to respect the maximum string length of 65534 characters.<br />
ADAPT00215189<br />
Description:<br />
A single sign-on to PeopleSoft does not work as expected.<br />
Patch ID: 35737925<br />
The cause of the problem is that Crystal Reports does not use the current PeopleSoft session information for log ons.<br />
New Behavior:<br />
The problem is resolved.<br />
Known Limitations:<br />
For SSO, if the DSN is set to use 3 tiers through an application server, the PeopleSoft ODBC driver will not pick up the db/appsrv<br />
information from the registry. A DSN set up for 2 tiers through the app server continues to work as expected.<br />
ADAPT00216638<br />
Description:<br />
Patch ID: 35830058<br />
When a user logs on to Crystal Enterprise using Active Directory authentication, logon time is longer than usual and may result in a<br />
timeout.<br />
The logon delay is caused by improper DNS queries that are formed in certain Active Directory configurations; the extra effort made in<br />
resolving the name causes the delay.<br />
New Behavior:<br />
A registry key controls this functionality.<br />
ADAPT00222956<br />
Description:<br />
Patch ID: 35847920<br />
When a native report is based on an IBM DB2-stored procedure and set to use the custom data source option, the following error is<br />
returned: "The table could not be found."<br />
The cause of the problem is that the driver searches for a stored procedure if it does not recognize the table type.<br />
New Behavior:<br />
If a table type is unknown and the fully qualified name doesn't contain "proc()", the driver searches for the table name as if it is a table<br />
(rather than a stored procedure). If the table is not found, then the driver searches for a stored procedure.