This is a great property.

As I understand it, this will allow me to access more than one databases at a time, in any directory on my hard disk. That would make ElevateDB as flexible as DBISAM with regards to database location.

I have a couple of questions:

1: Does the default Session become unusable when this property is set to true? Do I have to create a new TEDBSession?

2: When I create a new session and connect it to an existing database, do I have to issue an 'ALTER DATABASE XXX PATH "C:\DatabasePath"', to indicate just which database directory I am using for this session? (I have a situation where our sales reps all around the country, backup their databases to our central server, and then I can download those databases to my computer and look at each database individually. Very easy with DBISAM, just change the DatabaseName property).

Richard

>1: Does the default Session become unusable when this property is set to true? Do I have to create a new TEDBSession?

No but as with any other session you have to set the appropriate properties - LocalConfigPath, LoginUser, LoginPassword, LocalEncryptionPassword etc

>2: When I create a new session and connect it to an existing database, do I have to issue an 'ALTER DATABASE XXX PATH "C:\DatabasePath"', to indicate just which database directory I am using for this session? (I have a situation where our sales reps all around the country, backup their databases to our central server, and then I can download those databases to my computer and look at each database individually. Very easy with DBISAM, just change the DatabaseName property).

Only if the database path has changed. ElevateDB works differently to DBISAM. The database path is stored in the configuration file. What you have to give the session is the path to this file.

You can do it the way you suggest - keep altering the database path so its pointing to a different set of tables - or simple set up a database for each one (eg using the sales rep's name) and switch between those. The latter approach gives you the advantage of haveing several of them open simultaneously.

Roy Lambert [Team Elevate]

Richard,

<< 2: When I create a new session and connect it to an existing database, do
I have to issue an 'ALTER DATABASE XXX PATH "C:\DatabasePath"', to indicate
just which database directory I am using for this session? (I have a
situation where our sales reps all around the country, backup their
databases to our central server, and then I can download those databases to
my computer and look at each database individually. Very easy with DBISAM,
just change the DatabaseName property). >>

You might want to look into using the TEDBEngine.ConfigMemory property that
is new in 2.04.  This is really the property that you want, since it will
allow you to keep the configuration in memory in the application, and use
the CREATE/ALTER DATABASE statement to keep changing the location of the
database that you're accessing without constantly updating an on-disk
configuration file.  However, in order to use this property, you have to
make sure that you aren't also using a disk-based configuration file against
the same databases with another application or process, like the EDB Server.
Basically, all client engines must be using ConfigMemory when accessing the
same database(s).

--
Tim Young
Elevate Software
www.elevatesoft.com