CE10WIN_EN_SP6
CE10WIN_EN_SP6
CE10WIN_EN_SP6
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>CE10WIN</strong>_<strong>EN</strong>_SP2<br />
Rich Text Format<br />
ADAPT00204186 Patch ID: 36503005<br />
Description:<br />
When a report is exported to RTF or Microsoft Word format with the "Use Default Margins" setting enabled in the page setup area of<br />
Crystal Reports 10, the report sets the paper size to [8.5 * 11.5], rather than [8.5 * 11].<br />
The problem is that the default paper size was mistakenly declared as [8.5 * 11. 5].<br />
New Behavior:<br />
This problem is resolved.<br />
Scheduling time<br />
ADAPT00324251 Patch ID: 36520282<br />
Description:<br />
If between 12 AM and 1 AM a user schedules a report through the Crystal Enterprise Java ePortfolio, the report instance’s next run<br />
time is scheduled 11 hours ahead. This behavior occurs only when reports are scheduled to run "Now" (immediately).<br />
For example, if a schedule for the option "Now" is submitted at 12:24 AM, the next run time will be 11:24 PM the same day.<br />
New Behavior:<br />
This problem is resolved and has been applied to the Java SDK core file (cecore.jar).<br />
Separated values<br />
ADAPT00301335 Patch ID: 36395145<br />
Description:<br />
When users export to CSV format from Crystal Reports or Crystal Enterprise, if the designated field delimiter character is in a field tha<br />
is being exported, the field is exported incorrectly. This problem can result in field misrepresentation, if the CSV file is used in<br />
applications (such as Microsoft Excel).<br />
The cause of the problem is that the field delimiter character fails to be doubled (or consistently recounted) when it appears in a field.<br />
The result is that the consumer of the separated values becomes confused over whether the field is ending.<br />
New Behavior:<br />
Delimiters that are used in exported fields are doubled when the file is exported, to prevent this problem.<br />
Server functionality<br />
ADAPT00262235 Patch ID: 36112910<br />
Description:<br />
When users export a report, which contains subreports that use shared variables, to any record-based format (e.g.: Microsoft Excel,<br />
Text, etc.), the subreport prompts for the data source. Or, when exporting a successful instance of such a report through a viewer in<br />
Crystal Enterprise, the first export fails.<br />
The problem is that the cached variable state is not retrieved properly when exporting subreports to record-based formats.<br />
New Behavior:<br />
A new method of mapping formula states has been introduced for all record-based export formats. This problem is resolved.