Gregory,

<< I'm a DBISam user with a very vague understanding of EDB. It seems like I
might have misunderstood the purpose of the Config file in EDB . I was under
the impression that the config file was much like lock control file in the
BDE/Paradox engine where all installations of the BDE in a worgroup had to
point to the same lock control file. >>

The config file does have a hidden lock file also, but it is simply an empty
shell file (zero byes) that is used to implement the multi-user locking.

<< The documentation that caused me to draw this conclusion was : >>

Yes, that is correct.  Certain locking that is done on each database is
determined by when each session connects to the config file (and obtains a
lock in the hidden config lock file).  If you are using different config
files, then you are using different config lock files, thus making the locks
incompatible with each other if they are, in turn, accessing the same
physical database.

<< 1. Do all installations of an EDB app in a LAN accessing the same
database ( under file sharing Local) have to point to the same config file ?
>>

Yes.

<< If so, can this be done programmatically such that the end-user does not
have to bother with this. >>

Sure.  A lot of customers just use the application .exe path as the config
path, and that is what we recommend.

The only stipulation is that the database path that is specified via the
config file resolve to the same physical location for every multi-user,
file-sharing client application that is accessing that config file.  UNC
paths will resolve this, if mapping is an issue.

<< Or do we need to provide the end user with a means to configure the path
to the EDB config file in their own network enviroment (much like
BDE/Paradox) ? >>

You could, but it isn't necessary.

<< 2. Where would you typically place the EDB Config file ?  Program Folder,
APPData folder or Shared Documents folder ? >>

For multi-user, the application .exe path will work since you'll be storing
the .exe on the network in most cases (though, that's not a given).   For
local applications installed into the Program Files folder, then you'll need
to be Vista-aware and use something like the shared common AppData folder or
something similar that is truly writable for all local users of the machine.

Do all users need read and write access to the config file ? >>

Yes, if you need them to be able to modify the configuration by creating,
altering, or dropping any Configuration objects such as databases, users,
etc.  If not, then the configruation file can be read-only and EDB can
handle that just fine.

--
Tim Young
Elevate Software
www.elevatesoft.com

Wim,

<< I just "converted" my first dbisam 3.30 app from file sharing to client
server (also 3.30). I played a little bit with EDB before.  I think the step
from dbisam 3.30 file sharing to EDB (even in file sharing) is pretty big.
The step from dbisam 3.30 CS to EDB is more obvious.  With EDB weither you
use it as CS or file sharing, you MUST use the same configuration files.
Maybe you could elaborate on that aspect in one of your blogs and get more
users to upgrade. >>

I think the first article that I will be doing will focus on the
configuration files since they are, by far, the most confusing aspect to
existing DBISAM users that are migrating over.

--
Tim Young
Elevate Software
www.elevatesoft.com