CE90WIN_EN_SP5

CE90WIN_EN_SP3
Charting
ADAPT00116298
Description:
Patch ID: 36229129
Reports that contain funnel and pie charts, with the values shown on the chart as percentages, display the values in an incorrect
format in the chart's legend. For example, a currency value is listed in the legend as 12,345.00% when it should be $123.45.
New Behavior:
This problem is resolved.
Known Limitations:
This fix does not also provide a way for users to change the generic number format in the legend to another format.
In Crystal Reports 10, the Pie Chart Total Label may become incorrectly formatted as a malformed percentage. To work around this,
first select the desired Category for the label under the Numbers tab in the General Chart Options, then check the Show Values as
Percentage checkbox under the Data Labels tab and click OK.
COM SDK
ADAPT00255258
Description:
Patch ID: 36027011
When the Report Application Server (RAS) is overloaded, the RAS server slows down such that it causes a timeout in the browser or a
long delay in displaying a report.
The cause of the problem is that each request to the RAS server shares the server’s CPU. In addition, a high amount of context
switching occurs, which demands further CPU time.
New Behavior:
Users can apply querysrv.exe to control the number of concurrent jobs that are processed. Use the following command line switch:
(-maxrequestpool). This switch can help distribute CPU time evenly to the number of jobs set through the command line.
In addition, a registry key has been added to disable a lock in the crheapalloc.dll memory allocation library. This key reduces context
switching, so that RAS can process jobs quicker under a high load.
CRW designer
ADAPT00229562
Description:
Patch ID: 35932626
The error "Failed to open rowset" appears when running a Sybase 12.5 report that uses the native driver (crdb_p2ssyb10.dll). This
error occurs when a simple boolean formula is used in the record selection:
{Database Table.Database Field} = {Database Table.Database Field} AND {Database table.Database Field} = 1
The statement before the "AND" condition generates an incorrect SQL query. The SQL that is generated includes an extra "AND"
statement in the WHERE clause.
New Behavior:
This problem is resolved.