With DBISam (in shared file mode) you could set the Directory property
of the Database component and that would establish the location of the
data files.  Now in ElevateDB, the path to the data files is stored in
the Database Catalog file.  So, assuming shared file mode, how should I
manage environments where different users access the same physical data
folder through different paths (different drive mappings to the same
folder, a local shared folder vs connecting to that folder, etc.)?

As I understand it, the Catalog file gets created when you create the
Database.  Is there a way to programatically control where the Catalog
file gets created?

--
Gordon Turner
Mycroft Computing
http://www.mycroftcomputing.com

Gordon

>As I understand it, the Catalog file gets created when you create the
>Database. Is there a way to programatically control where the Catalog
>file gets created?

I think what you're looking for is TEDBEngine.ConfigPath

Roy Lambert wrote:
>
> I think what you're looking for is TEDBEngine.ConfigPath

Ahhh.  Thanks.

Now for the next step... When the program starts, it checks to make sure
the data files exist by querying Information.Tables (using the code from
the CreateDBDDL example).  However, when the program is connected to the
database from another workstation, this query fails with "ElevateDB
Error #300 Cannot lock Test database for shared access."  The program
sets Exclusive := False when opening the tables, so where else do I need
to set to test table existence successfully?

--
Gordon Turner
Mycroft Computing
http://www.mycroftcomputing.com

Gordon


Is a configuration file being created on each PC? If so that's your problem.

Roy Lambert

Roy Lambert wrote:
>
> Is a configuration file being created on each PC? If so that's your problem.

OK, but then how do I handle different users accessing the same data
files with different file paths?  When I try sharing the configuration
file, I get an error because the path does not exist on one of the
workstations.

--
Gordon Turner
Mycroft Computing
http://www.mycroftcomputing.com

Gordon


You have to use UNC paths. If they don't exist you're in serious trouble

Roy Lambert

Gordon,

<< OK, but then how do I handle different users accessing the same data
files with different file paths?  When I try sharing the configuration file,
I get an error because the path does not exist on one of the workstations.
>>

The configuration file simply exists (or will exist) at a specific location
on disk.  How you specify the path to that configuration file is handled
completely within the context of the TEDBEngine.ConfigPath property.  It is
no different than how you handled specifying a directory location of a
DBISAM database with DBISAM in terms of different users having different
drive letter/path names to the database directory.

However, one thing to keep in mind is that the database paths that are
stored in the configuration file for all defined databases *must* be
accessible by all users that will use those databases.   So, it is usually
best to simply use full path names without a drive letter or use UNC path
names for all path specifications for the defined databases.

--
Tim Young
Elevate Software
www.elevatesoft.com

Gordon

>OK, but then how do I handle different users accessing the same data
>files with different file paths? When I try sharing the configuration
>file, I get an error because the path does not exist on one of the
>workstations.

I just realised the obvious answer - put the configuration file in with the data and use UNC, but make sure Tim's not watching cos he doesn't want us making 1:1 relationships config:catalog:data

Roy Lambert

Roy,

<< I just realised the obvious answer - put the configuration file in with
the data and use UNC, but make sure Tim's not watching cos he doesn't want
us making 1:1 relationships config:catalog:data >>

I'm just saying that you may eventually find that it wasn't a good idea,
especially if you need to expand to more than one database.

However, on a serious note, it is much easier to deal with when the
configuration files (config file, lock file, log file) are separate from the
database catalog and table files.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


>However, on a serious note, it is much easier to deal with when the
>configuration files (config file, lock file, log file) are separate from the
>database catalog and table files.

Errrrr isn't the lock file EDBDatabase.EDBLck? If so it lives in the same dir as the catalog......

Roy Lambert