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 />
CRW designer<br />
ADAPT00141245<br />
Description:<br />
Patch ID: 35202978<br />
When the "Update Repository Objects" check box is enabled, an error occurs when opening a report that was created against an SQL<br />
command in the Repository.<br />
New Behavior:<br />
The report will no longer return an error when the "Update Repository Objects" check box is enabled. You should verify the report to<br />
ensure that the changes in the Repository will take effect.<br />
ADAPT00167576<br />
Description:<br />
Patch ID: 35384710<br />
Customized map layers cannot be saved in the Report Designer and Report Designer Component.<br />
New Behavior:<br />
The sequence of saving customization in map layers is corrected. Users can now save changes in map layers properly in the Report<br />
Designer and Report Designer Component.<br />
CSP Eportfolio<br />
ADAPT00163129<br />
Description:<br />
Patch ID: 35316070<br />
Opening an instance of a scheduled report that contains no data but has a subreport linked to a parameter field in the main report,<br />
results in the following error: "Cannot Open SQL Server." This error occurs because the datasource for the subreport is not properly set<br />
when the Print Engine detects that the main report contains no data.<br />
New Behavior:<br />
A new case has been added to ensure that the subreport datasource is valid even when the report contains no data. Scheduled report<br />
instances containing a subreport linked to a parameter field in the main report will now display without error when the instance<br />
contains no data.<br />
Known Limitations:<br />
This behavior is corrected only after applying this patch and rescheduling the report instances.<br />
Data Explorer<br />
ADAPT00103975<br />
Description:<br />
Patch ID: 34903305<br />
Reports created with a version of Crystal Reports earlier than version 9.0 are saved with all the connection properties. When these<br />
reports are used in Crystal Reports 9.0, all properties are passed into the crdb_odbc.dll to construct the connection string. When there<br />
is no change in these properties, there is no problem. However, a logon failure is caused when one of the properties (the database file<br />
path) is changed.<br />
New Behavior:<br />
The crdb_odbc.dll now uses SQLConnect instead of SQLDriverConnect to make the connection for the best ODBC driver. SQLConnect<br />
requires only three parameters: user name, password, and DSN. Other parameters will be ignored.
Change language