CE90WIN_EN_SP5
CE90WIN_EN_SP5
CE90WIN_EN_SP5
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>CE90WIN</strong>_<strong>EN</strong>_SP1<br />
Push Down<br />
ADAPT00123246<br />
Description:<br />
Patch ID: 35162114<br />
Crystal Reports is unable to retrieve data or records from Microsoft Access ODBC expression fields that are concatenated within a<br />
Microsoft Access query.<br />
New Behavior:<br />
Crystal Reports was returning Microsoft Access ODBC expression fields with a size of zero. This issue has now been resolved: the<br />
field size returns 64,000 of WChar for string fields if the field is detected as being zero in size.<br />
ADAPT00141458<br />
Description:<br />
Patch ID: 35156378<br />
When a user created a report from a Microsoft SQL Server stored procedure using ODBC, if the stored procedure used a parameter that<br />
was a Text data type, a blank window with the title "Enter Parameter Values" was returned when the user tried to enter the parameter<br />
value.<br />
New Behavior:<br />
A change has been made in the Crystal Reports ODBC driver to allow for parameters of Text type when a user reports from Microsoft<br />
SQL Server stored procedures.<br />
Query Builder<br />
ADAPT00122882<br />
Description:<br />
Patch ID: 34991534<br />
The tables in the FROM clause for RAS 9 queries are not in the same order as tables for RAS 8.5 queries.<br />
New Behavior:<br />
The tables in the FROM clause for RAS 9 queries are now arranged in an order similar to the tables for RAS 8.5 queries.<br />
ADAPT00134544<br />
Description:<br />
Patch ID: 35097567<br />
When using a left function in an SQL expression within Crystal Reports 9, connecting natively to DB2 and then setting the "Use Index<br />
or Server for Speed" causes the designer to fail with a GPF.<br />
New Behavior:<br />
The designer will no longer cause a GPF and the data will refresh correctly.<br />
ADAPT00164331<br />
Description:<br />
Patch ID: 35382600<br />
When you create a report that is based on an SQL Command and another table, and link the SQL Command and the other table, an<br />
error to appears the first time the report is refreshed. Any subsequent refreshes do not generate the error, and return the data as<br />
expected.<br />
New Behavior:<br />
This issue has been fixed.<br />
Reliability