Tim,

I have a database where all Tables shows me an EDB Error #100. I´m not able to open,
backup or anything else with that database. I have definitivly nothing copy manually. My
last backup was from Feb. 1st. If I drop the database and restore it from this backup,
then it seem to work fine. But then I miss the data until now.

How can this error happen? I tried to open the database and select the wrong EDB Manager -
the Version 1.09. I got an error and saw that I have the wrong Manager. Can it be that I
have damaged it there?

How can I bring the catalog and the tables back in sync?

Please Help me

regards
Michael

Michael,

<< I have a database where all Tables shows me an EDB Error #100. I´m not
able to open, backup or anything else with that database. I have definitivly
nothing copy manually. My last backup was from Feb. 1st. If I drop the
database and restore it from this backup, then it seem to work fine. But
then I miss the data until now. >>

What is the actual error message that you're seeing ?  Can you send me a
copy of the database catalog and some of the table files to look at ?

<< How can this error happen? I tried to open the database and select the
wrong EDB Manager - the Version 1.09. I got an error and saw that I have the
wrong Manager. Can it be that I have damaged it there? >>

No, 1.09 will simply refuse to open the database catalog if it was updated
using a later version of EDB.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<<What is the actual error message that you're seeing ?  Can you send me a
copy of the database catalog and some of the table files to look at ?>>

This is the message I see:

---------------------------
ElevateDB Manager
---------------------------
ElevateDB Error #100 There is an error in the metadata for the table ProtocolMember (The
internal version does not match the version in the configuration or catalog)
---------------------------
OK   
---------------------------

Find attached the catalog and some Tables.

Regards
Michael

Michael,

<< This is the message I see: >>

Are you sure that the only thing that happened with these tables is that you
tried to open them using 1.09 ?

These table files have an incorrect check sum in them for the meta data,
meaning that they are from 2.03, and that they were originally used with a
different version of the database catalog.  It looks like the database
catalog was copied over from a different version of the database.

--
Tim Young
Elevate Software
www.elevatesoft.com