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>_SP1<br />
Saved data<br />
ADAPT00102001<br />
Description:<br />
Patch ID: 35321914<br />
When a user drills down on a report with saved data, the user is prompted to enter database logon information for the hidden<br />
subreport.<br />
New Behavior:<br />
The architecture is changed to not prompt the user for the database logon information, even when a subreport is hidden. Therefore,<br />
users do not need to log on to the database again for subreports when users drill down. The problem is fixed.<br />
Scheduling destination<br />
ADAPT00122224<br />
Description:<br />
Patch ID: 35179104<br />
The ending boundaries for MIME headers were not generated when a user scheduled reports to a SMTP destination.<br />
New Behavior:<br />
The ending boundary was added to the MIME encoded message. When a user schedules a report to a SMTP destination, an<br />
RFC-compliant ending boundary appears at the end of the MIME header.<br />
ADAPT00141190<br />
Description:<br />
Patch ID: 35153899<br />
When a user scheduled a report in ePortfolio to be exported in Character-Separated Values format, a delimiter value of NULL could<br />
not be selected.<br />
New Behavior:<br />
A change has been made to ePortfolio to allow a value of NULL for the delimiter when a user schedules a report to the<br />
Character-Separated Values format.<br />
ADAPT00154860<br />
Description:<br />
Patch ID: 35265485<br />
If a report name contains accented characters such as (ï,ä,ê,ë) and the body of the message is NULL, the filename of the report becomes<br />
corrupted when scheduled to SMTP destination. This corruption occurs because the mail server interprets the filename of the<br />
attachment as US-ASCII encoding if the mail message body is empty.<br />
New Behavior:<br />
The SMTP destination has been modified to use UTF-8 for filename encoding, so now the mail server interprets the accented characters<br />
correctly.<br />
SDK<br />
ADAPT00116137<br />
Description:<br />
Patch ID: 34954334<br />
In Microsoft Visual Basic 6 application using the Report Designer Component, reports based on hierarchical (shaped) ADO recordsets<br />
are displaying ttx sample data rather than data in recordset.<br />
New Behavior:<br />
This problem occurs if hierarchical rowset is not enabled. Once enabled, reports are able to successfully display data contained within<br />
hierarchical (shaped) ADO recordsets.
Change language