Hedley,

<< I notice that if I create a new EDBConnection object and point the
ConfigPath to a new empty folder, it creates the EDBConfig file in there for
me. I can then connect to the "Configuration" database using the default
Administrator / EDBDefault user, and call "CREATE DATABASE xxx" to create a
new database in a sub-folder and then I'm good to go... >>

Yep, and if you move databases around, then just use an ALTER DATABASE to
point to the new database location.

<< As my application allows users to create multiple databases which are
entirely separate from each other, does it matter if I create a new
EDBConfig file (which=a session?) for each database, rather than having a
single EDBConfig file? >>

It depends upon how you intended to use the configuration-level items like
user security.  If you want the users/roles to be the same for all
databases, then you should use one configuration file with multiple
databases defined in it.  If you want everything to be separate for each
database, including user security, then you should use a separate
configuration file per database.  However, it is a bad idea to put the
actual configuration file in the same directory as the database directory.
With such a setup, it's too easy to accidentally blow away the configuration
file if you only want to delete the database files.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim.