I have just received notification of Version 2.14 Build 3.
There is a fix to a problem I have been having relating to Creating
Database Migrators Incorrectly.

I have already wasted hours of my time looking into this issue.

Here are some practical ways that will reduce the frustration levels :

1. When an error is written in the Manager the full path is output.
Currently the path is truncated using .. notation.
However the width taken up by the existing error message is only about
60% of my screen real estate.

Why is the path being unnecessarily truncated?

2. In the Help file for the manager add all the error messages that can
arise. And give a resolution.

Pretty obvious I would have thought.

Regards,
  Peter Evans

Peter,

<< 1. When an error is written in the Manager the full path is output.
Currently the path is truncated using .. notation.  However the width taken
up by the existing error message is only about 60% of my screen real estate.

Why is the path being unnecessarily truncated? >>

It's not being truncated, it's just not being converted from a relative path
name into absolute path name.  However, when I fixed this last issue with
the paths, I also included a fix for this, so the relative path names are
converted into an absolute path name.  IOW, this is already taken care of.

<< 2. In the Help file for the manager add all the error messages that can
arise. And give a resolution. >>

Which error messages are you referring to ?  The ElevateDB engine error
messages are already all included in the SQL manual that is set up with the
EDB Manager.

Tim Young
Elevate Software
www.elevatesoft.com