Tim,

I am using EDB v1.07b3.  If a try to run a program against the database that has been
compiled with v1.07b2, I receive a version number mismatch on the EDBCat file.

The same program compiled with v1.07b3 is OK.  The structure of the database has not changed.

Is this expected?  What do I need to do to run the v1.07b2 program?

Richard Harding

Version,

<< I am using EDB v1.07b3.  If a try to run a program against the database
that has been compiled with v1.07b2, I receive a version number mismatch on
the EDBCat file. >>

Are you sure about the version numbers ?  There were no catalog changes
between B2 and B3 since we don't do catalog changes between builds, only
between minor version releases.  In fact, our automated test framework uses
databases created with version 1.00 with no problem - the catalog reading
works on any version.  However, once a catalog is written out using a later
version, then any prior version of EDB cannot read it and will get the error
that you describe.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim.

I manage to get myself into something of a mess with version numbers every now and again
to do with backups and restores and I don't understand what is going on.

If it happens again, I'll try to document it more carefully.

Richard Harding

Richard,

<< I manage to get myself into something of a mess with version numbers
every now and again to do with backups and restores and I don't understand
what is going on. >>

Just remember, older versions cannot access any catalog that has been
updated using a newer version, and that includes a newer version performing
a restore, even if the catalog being restored is from an older version.
EDB always writes out the catalog using the version that is performing the
restore.

--
Tim Young
Elevate Software
www.elevatesoft.com