Stephan,

<< I am sorry that it looks like I hurt you. I seems that I am not able to
explain you what I mean. Sorry for that, I don't want to keep you off from
your work. >>

I understand what you mean.  What I'm saying is that I'm not sure if you
understand how EDB works just yet.

If one of your users deletes the entire database directory, then this is
what will happen in your application:

1) When you open the database, EDB will recreate the database directory and
create an empty database catalog.

2) When you try open any table in the database, EDB will issue an exception
saying that the table doesn't exist.

So, while you won't get an exception with 1), you will receive one with 2)
indicating that something is wrong.

However, if the user deletes all of the table files *only*, but not the
database catalog (.edbcat) file in the database directory, then EDB will not
issue an exception and the tables will simply be empty.

But, again, this is all academic because you should not be moving around
tables physically using OS commands, and you should definitely tell your
users not to do so.  The reasons for this are numerous, but you can cause
all sorts of corruption to the RI and other issues with mismatched table and
catalog files by doing so.

--
Tim Young
Elevate Software
www.elevatesoft.com