Tim,

Since I have installed version 1.06, I have received a number of #100 errors.

Error #100 - (ElevateDB Error #100 There is an error in the metadata for the table Stock
(Signature, password, or character set (ANSI/Unicode) mismatch, or version mismatch)

I am not sure of the circumstances that create this.  It happens in both the EDB Manager
and my application programs.

To recover I restore the database from backup.

(Last time this happened it was because I installed the Unicode version of ElevateDB).

Any ideas on what is happening?

--
Richard Harding
Windella Computer Knowhow
28 Freeman Drive
Lochinvar NSW 2321
Phone:   61 2 4930 7336
Mobile:   0419 016 032
email:   rharding@wck.com.au

Richard,

<< Since I have installed version 1.06, I have received a number of #100
errors.

Error #100 - (ElevateDB Error #100 There is an error in the metadata for
the table Stock (Signature, password, or character set (ANSI/Unicode)
mismatch, or version mismatch)

I am not sure of the circumstances that create this.  It happens in both
the EDB Manager and my application programs.

To recover I restore the database from backup.

(Last time this happened it was because I installed the Unicode version of
ElevateDB). >>

Are you restoring from backups where the catalog may be different than the
table in terms of its structure ?   That, or copying over the table/catalog
files individually is the only thing I can think of that would cause a table
metadata mismatch like that.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim.

Yes, I was trying to restore a backup that had a modified structure on one of the tables.

The version property of the table that is displayed in the ElevateDB Manager - that
appears to be a different concept to the version that the error message is referring to in
the message "(Signature, password, or character set (ANSI/Unicode) mismatch, or version
mismatch)".  Is this correct?

How can we determine what version of the database we are accessing.

Richard Harding

Richard,

<< Yes, I was trying to restore a backup that had a modified structure on
one of the tables. >>

Yes, that will be an issue if the table structure in the catalog is
different.

<< The version property of the table that is displayed in the ElevateDB
Manager - that appears to be a different concept to the version that the
error message is referring to in the message "(Signature, password, or
character set (ANSI/Unicode) mismatch, or version mismatch)".  Is this
correct? >>

Yes.  There is an internal table version number that we increment whenever
the table structure changes in a way that affects the actual table files.
We use this version number to make sure that the table files always match
what the database catalog has registered as the current version number.   If
they don't match, then something has gone wrong.

<< How can we determine what version of the database we are accessing. >>

You really can't see these internal version numbers at this time.  I will
see if can add them to the Information schema Tables table so that you can
at least see what the catalog expects.   However, it won't do much good
without being able to see the table versions in the backups also, so that
will need changed also.

--
Tim Young
Elevate Software
www.elevatesoft.com

>>You really can't see these internal version numbers at this time.  I will
see if can add them to the Information schema Tables table so that you can
at least see what the catalog expects.   However, it won't do much good
without being able to see the table versions in the backups also, so that
will need changed also.


Thank you!!!

--
Richard Harding