Tim,

Trying to open the database posted by Ian Branch on another thread, I get
the following error message:
"ElevateDB Error #100 There is an error in the metadata for the catalog
tutorial (The catalog file ID is invalid)"

However, the error only appears on the first try.
If I try to open the DB again, there is no error and I can open the database
and read/edit the data normally. This happens not only in EDBM (ElevateDB
Manager) but also and in a test app I wrote.

I suspect I'm not doing things the correct way. What I did was:
- with EDBM, created a new database named "tutorial"
- expanded the files Ian posted and copied them all to the directory created
by EDBM for the "tutorial" database

Can this be done this way?
What is the recommended procedure to open a database created on another
system?

--
Fernando Dias

Fernando,

<< Trying to open the database posted by Ian Branch on another thread, I get
the following error message:

"ElevateDB Error #100 There is an error in the metadata for the catalog
tutorial (The catalog file ID is invalid)"

However, the error only appears on the first try. If I try to open the DB
again, there is no error and I can open the database and read/edit the data
normally. This happens not only in EDBM (ElevateDB Manager) but also and in
a test app I wrote.

I suspect I'm not doing things the correct way. What I did was:
- with EDBM, created a new database named "tutorial"
- expanded the files Ian posted and copied them all to the directory
created by EDBM for the "tutorial" database

Can this be done this way? >>

No.  You need to backup the database (with the catalog included) and then
restore it into the database that you have created.  The fact that you can
open the database the second time is a bug that needs to be fixed.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fernando,

<< No.  You need to backup the database (with the catalog included) and then
restore it into the database that you have created.  The fact that you can
open the database the second time is a bug that needs to be fixed. >>

Actually, that is incorrect also (I'm a little busy right now and so I'm
missing things occasionally) .  You need to make sure to have the
configuration file from the installation also (which Ian provided).  It
provides the users and roles that are required for having proper access to
the database.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> You need to make sure to have the configuration file from the installation
> also (which Ian provided).  It provides the users and roles that are
> required for having proper access to the database.

Using the configuration file Ian provided I could not see any database and
that's why I tryed to open it using that "alternative" way... I suspect that
the configuration file he provided is not the same he used to create the
database. Can you please take a look into it and confirm that?

--
Fernando Dias




>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Fernando,

<< Using the configuration file Ian provided I could not see any database
and that's why I tryed to open it using that "alternative" way... I suspect
that the configuration file he provided is not the same he used to create
the database. Can you please take a look into it and confirm that? >>

There aren't any databases defined in the configuration file that he
included in the .zip file.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Thank you.
I think I get the general idea now about the configuration file / catalog
files.

--
Fernando Dias

Hello Tim

I've been reading about config-files, catalogues and about moving EDB-databases from one system to another. I just want see if I understand how it
works.

1. In EDB you cannot simply copy the databasefiles from one PC to another. You would have to make a backup on one PC and than create the
database on the other PC and then restore the backup. This is necessary because the configuration file is intertwined with the database and has to
be correctly updated.

2. In DBISAM on the other hand it is possible to simply copy the database-catalogue and the database-files to another PC and then use the database
directly.

3. In a simple single-user desktop application users treat their databases like documents. They might want to copy their databases back and forth
between a laptop and a stationary PC. This is easy if the databasemanager works like DBISAM but more complicated if it works like EDB.

4. Is EDB intended more for office-applications than for simple single-user desktop applications as in <3> above?

5. For simple single-user desktop applications that works like in <3> above, it would be better to continue to use DBISAM?

6. For how long will you continue to support DBISAM?

Best regards

Mats Berggren


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Fernando,

<< Trying to open the database posted by Ian Branch on another thread, I get
the following error message:

"ElevateDB Error #100 There is an error in the metadata for the catalog
tutorial (The catalog file ID is invalid)"

However, the error only appears on the first try. If I try to open the DB
again, there is no error and I can open the database and read/edit the data
normally. This happens not only in EDBM (ElevateDB Manager) but also and in
a test app I wrote.

I suspect I'm not doing things the correct way. What I did was:
- with EDBM, created a new database named "tutorial"
- expanded the files Ian posted and copied them all to the directory
created by EDBM for the "tutorial" database

Can this be done this way? >>

No.  You need to backup the database (with the catalog included) and then
restore it into the database that you have created.  The fact that you can
open the database the second time is a bug that needs to be fixed.

--
Tim Young
Elevate Software
www.elevatesoft.com

Mats,

<< 1. In EDB you cannot simply copy the databasefiles from one PC to
another. You would have to make a backup on one PC and than create the
database on the other PC and then restore the backup. This is necessary
because the configuration file is intertwined with the database and has to
be correctly updated. >>

No, this was only the case in the first and second betas.  It is no longer
the case.  You can copy databases around anywhere you like, as long as you
include the edbdatabase.edbcat catalog file and the table files that you
want.

<< 2. In DBISAM on the other hand it is possible to simply copy the
database-catalogue and the database-files to another PC and then use the
database directly. >>

DBISAM doesn't have catalog files, only table files.

<< 3. In a simple single-user desktop application users treat their
databases like documents. They might want to copy their databases back and
forth between a laptop and a stationary PC. This is easy if the
databasemanager works like DBISAM but more complicated if it works like EDB.
>>

Frankly, I wouldn't encourage users to copy either DBISAM or EDB files
around like that.  It's really easy to screw something up and lose their
data completely.  I would provide a facility in your application for moving
data back and forth.

<< 6. For how long will you continue to support DBISAM? >>

For at least another year.

--
Tim Young
Elevate Software
www.elevatesoft.com