18.08.2013 Views

CE90WIN_EN_SP5

CE90WIN_EN_SP5

CE90WIN_EN_SP5

SHOW MORE
SHOW LESS

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>_SP2<br />

ADAPT00195439<br />

Description:<br />

Patch ID: 35824893<br />

When setting the data source location on a report that is based off an IDAPI database, an error message appears when users edit the<br />

"Data File:" property of the connection. The error message reads: "Some tables could not be replaced, as no match was found in the<br />

new data source. Please specify the table required for any unmodified tables."<br />

The error appears because the table name is taken from the file name; when the file name changes, the old table name cannot be found.<br />

New Behavior:<br />

The drivers no longer match the file name to the table name.<br />

ADAPT00199005<br />

Description:<br />

Patch ID: 35621459<br />

When a report is based on a query file that queries a DB2 ODBC data source, the prompt for the database log on displays the default<br />

value (the database name) when a database connection is required. This behavior is incorrect.<br />

New Behavior:<br />

The default value (database name)is no longer shown. In its place is a choice of aliases that have been configured in the DB2 client.<br />

ADAPT00201569<br />

Description:<br />

Patch ID: 35666358<br />

When verifying the database in a report based off a DBISAM database, the following error message appears: "The database table<br />

cannot be found. Proceed to remove this table from the report?" The error message appears because the DBISAM driver<br />

does not support the catalog. In that case, rather than return the catalog, the driver returns the physical path to the database file. When<br />

the path is used for the table name, it causes the error.<br />

New Behavior:<br />

If the catalog is detected as a path, it is removed completely; therefore, the driver no longer returns the database path in the full table<br />

name, in place of the catalog.<br />

Known Limitations:<br />

This fix works only with newly created reports.<br />

ADAPT00205949<br />

Description:<br />

Patch ID: 35692063<br />

Viewing a report on demand that contains a SQL Command from the Crystal Repository creates a looping logon prompt, for certain<br />

tested databases.<br />

The problem is caused by logon credentials that are being passed incorrectly.<br />

New Behavior:<br />

This problem is resolved.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!