Hi,

I'm currently evaluating ElevateDB and its proving to be capable of doing everything I need it to do and it works first time unlike one or two other embedded databases I have trialed.

I'm planning on distributing an app over the web. I've noticed that ElevateDB doesn't store all tables inside a single database file. Instead there are individual files for each table. I'm concerned that the more files that a user can poke around and find (and possible delete or move) that there is more that could go wrong than if there was just one database file.

Is this a problem at all? Are there any ElevateDB users out which sell a product over the web and do you encounter any problems? Is there anything you can do to hide the files about from the standards windows stuff?

Thanks

Jeff

Jeff,

> I'm currently evaluating ElevateDB and its proving to be capable of doing everything I need it to do...

You will love it

Concerning your question: there is no need to ship all database files
together with your application.

Normally you use a procedure in your app, that
1. sets the path for the config-file and creates the database.
2. executes a script creating all tables, views, indexes, procedures
etc. for this newly created database.

You can automatically create this script by reverse-engineering the
database.

Another way is:
1. like before
2. Ship the catalog file and copy it into your database folder.

When opening the database, all tables will be created automatically.
The disadvantage of this way is, that all seed values of Autoinc-ID's
match the Id's already created in the database on your computer.

Hope that helps.

Uli

Jeff,

<< Is this a problem at all? Are there any ElevateDB users out which sell a
product over the web and do you encounter any problems? Is there anything
you can do to hide the files about from the standards windows stuff? >>

I wouldn't worry about it too much, unless your users have a track record of
messing around with the contents of your database directory.  Is that the
case with your application ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Jeff,

> I'm concerned that the more files that a user can poke around and find
> (and possible delete or move) that there is more that could go wrong
> than if there was just one database file.

> Is this a problem at all? Are there any ElevateDB users out which sell
> a product over the web and do you encounter any problems? Is there
> anything you can do to hide the files about from the standards windows stuff?

I have thousands of users and never had a problem with them fiddling with the database files.

Regards,

Steve

Hi Uli,

Thanks for the tips they are handy to know. Sounds like the catalog file stores the data dictionary in itself.

Jeff

Hi Tim,

<<I wouldn't worry about it too much, unless your users have a track record of
messing around with the contents of your database directory.  Is that the
case with your application ?>>


Its not the case with my app it was just a concern I had.

Jeff

Hi Steve,

>>I have thousands of users and never had a problem with them fiddling with the database files.<<

Thats just the answer I am after. Thank you.

Jeff

Jeff,

> Thanks for the tips they are handy to know. Sounds like the catalog file stores the data dictionary in itself.

Yes, all database objects are stored there.

Uli

Jeff,

<< Its not the case with my app it was just a concern I had. >>

If your users aren't known to mess about with the contents of your app's
directories, then you should be fine.

--
Tim Young
Elevate Software
www.elevatesoft.com