Support

Release Notes for Report Commander 2.5

Article ID: K00000553
Last Updated: June 26, 2017

Applies To

Report Commander 2 Versions 2.5 and later

Summary

This article describes the changes included in Report Commander 2.5, released on June 26, 2017.

Note: This is a free update for all adTempus 2 users. No license update is required.

Upgrading

If you are upgrading from a previous 2.x version, run the installer to upgrade your existing installation in place. It is not possible to install this release side-by-side with an earlier 2.x release.

If you are upgrading from version 1.x, see the download page and the user guide for installation and upgrade information.

Obtaining the Update

See the download page to download the latest version of Report Commander. The setup program will update your installation.

Changes in This Update

This release incorporates the latest version of the Crystal Reports runtime, and corrects issues discovered since version 2.4. See article K00000544 for changes in version 2.4.

The following changes are included in this update:

Crystal Reports Runtime Update

Report Commander is updated to use version 13.0.20 of the Crystal Reports runtime from SAP. Crystal Reports 2016 features are now supported in Report Commander.

General

"Maximum report processing jobs limits" error when running multiple instances of Report Commander	CR00007280 Defect
Running several instances of Report Commander at the same time or in quick succession may produce error "The maximum report processing jobs limits configured by your system administrator has been reached" For more information see Knowledge Base article K00000551.

Missing parameters error if main report does not return data	CR00007281 Defect
If the main report does not contain any data, and a subreport has one or more parameters that are set from data in the main report, Report Commander gives a missing parameters error when the report is executed.

Database not found when using file-based data source with relative path	CR00007282 Defect
If a report uses a file-based data source (such as Microsoft Access) and the path to the data source is specified relative to the location of the report, report execution fails.