Hi,

In a file sharing mode environment, is it better to put the configuration file in each workstation or just to have one configuration file in the database
folder on the server machine?  Which approach is recommended?

Abdulaziz

>In a file sharing mode environment, is it better to put the configuration file in each workstation or just to have one configuration file in the database
>folder on the server machine? Which approach is recommended?

You MUST put ONE copy of the configuration file in a directory which ALL users can access otherwise if you put one on each workstation then only one user at a time will be able to access the tables.

Tim also suggests (and I agree) that you don't want to put it in with the data. So one copy in a directory on the server but not the data directory. If necessary create a separate directory for it.

Roy Lambert

Roy

<<Tim also suggests (and I agree) that you don't want to put it in with the data. So one copy in a directory on the server but not the data directory.
If necessary create a separate directory for it.>>

Any reason why not to put it with the DB directory?

Abdulaziz,

<< In a file sharing mode environment, is it better to put the configuration
file in each workstation or just to have one configuration file in the
database folder on the server machine?  Which approach is recommended? >>

The same configuration file must be shared by all sessions that are
accessing the same database(s).  You cannot have the same application using
multiple configuration files, irregardless of whether the application EXE is
installed locally on each workstation or shared off of the file server.

Application --> Configuration File --> Database(s)

http://www.elevatesoft.com/edb1sql_architecture.htm

The configuration file doesn't just store databases, users, roles, and jobs,
it also controls the locking related to databases, users, roles, and jobs.
Think of it like you would a database catalog file - if two different
applications use two different database paths, and subsequently two
different database catalog files, then one won't see the other's locks,
changes, etc. with respect to what is stored in the database catalog files.

--
Tim Young
Elevate Software
www.elevatesoft.com

Another question, we normally put the application in a folder on server that is READ-ONLY folder, and make shortcut on the desktop of the other PCs
over the LAN to the application.  If I put the configuration file on that folder would it be a good idea?

<<Another question, we normally put the application in a folder on server that is READ-ONLY folder, and make shortcut on the desktop of the other
PCs
over the LAN to the application.  If I put the configuration file on that folder would it be a good idea?>>

I guess this will not work since the EDB engine will be writing some data to it like locks..Etc.

Abdulaziz,

<< Another question, we normally put the application in a folder on server
that is READ-ONLY folder, and make shortcut on the desktop of the other PCs
over the LAN to the application.  If I put the configuration file on that
folder would it be a good idea? >>

It will work, but it will make it impossible to change any of the database
definitions, users, roles, etc. since the configuration will be treated as
read-only.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

<<It will work, but it will make it impossible to change any of the database
definitions, users, roles, etc. since the configuration will be treated as
read-only.>>

We do all sort of users privileges through the application.  In fact we use the FAT-CLIENT module were all the business is in the application itself.  So
there is nothing in the DB but the data.    If we can but the configuration file in the same folder with application without affecting the EDB engine
locks and stuff it will be the idle solution for us.