Release Notes

REA 9.13

Released July 7, 2008

Database Version

This release includes a database upgrade to schema version 1.69. This upgrade is required. It will:

The upgraded database will continue to work with older versions of REA back to version 9.8.

Integrated MapPoint Mapping

This version integrates Microsoft MapPoint with REA. The MapPoint/REA window, displayed within REA, can automatically locate and map addresses for the major REA record types. It can search for records with addresses in a given geographic area. Most major features of MapPoint, such as route planning, are available within REA.

To use MapPoint integration, you must have a copy of Microsoft MapPoint purchased separately. It has been tested with MapPoint 2006; we haven't tried older versions. Both the North American and European versions of MapPoint (or both simultaneously) are supported.

Other Changes

Bugs Fixed

REA 9.12.2

Released June 6, 2008

Database Version

This release includes a database upgrade to schema version 1.68. This upgrade is required. It will:

The upgraded database will continue to work with older versions of REA back to version 9.8.

New Features

Bugs Fixed

REA 9.12.1

Released March 7, 2008

This is a bug-fix release to correct a problem with Outlook synchronization.

REA 9.12

Released March 4, 2008

Database Version

This release includes a database upgrade to schema version 1.67. Upgrading the database is optional, but doing so will:

The upgraded database will continue to work with older versions of REA back to version 9.8.

Account Lockout on Windows Server 2003

Some users have experienced problems with account lockout when running reports using SQL Server 2005 on Windows Server 2003. Typical problems include a "Login failed" error message when trying to run any report, and user being occasionally unable to log in to REA using a valid login and password.

This is due to an interaction between SQL Server 2005, Windows Server 2003, and the REA Report Engine (really the Crystal Reports runtime). SQL Server 2005 introduced a new feature permitting Windows Server 2003 administrators to have SQL Server accounts automatically locked out after repeated failed login attempts. Unfortunately, the Crystal Reports runtime, when loading a report, makes a large number of invalid login attempts for no really good reason. This can trigger account lockout for whatever user last optimized the report.

In this release we've tried to work around the problem by turning off policy checking for SQL Server logins in REA. This workaround has no effect on your Windows Server password policy for Windows logins. It may have implications for the security of your SQL Server database, but things are no worse than they were under SQL Server 2000.

Microsoft Office Integration

This version of REA extends our Microsoft Office integration:

Other Changes

Bugs Fixed

Release notes for older versions