Okay, here is one. Looked through the newsgroups, but limited that
effort to half an hour.

I have three sessions, each with their own database.

During design-time:

When I set the database Connected property to TRUE for either sessions
one or two, there is no problem. Btw, when I connect one database,
automatically the other session(s) close.

When I set the database Connected property to TRUE for the third
database, connected to the third session, I get the "#300: cannot lock
the database for shared access."

This third database and session are identical to the second one, with
only their names changed. So both sessions point to the same folders.
All other sessions are closed when this third database is opened. The
connected third session does connect properly, without error. Just when
I open the database connected to it, that I get the error.

Any pointers from others who went through hell? Thx!

Was using 2.06 build 1.

Upgraded to 2.08 build 3. Problems solved.

Could it be they peddled me a trial version, btw? Evil!

Dom,

<< When I set the database Connected property to TRUE for either sessions
one or two, there is no problem. Btw, when I connect one database,
automatically the other session(s) close. >>

This sounds like a SessionName issue where you've got database components
connected to the wrong session.  EDB will only automatically close a session
component if you close the TEDBEngine component.  That's it, and at no other
time will it automatically close a session.

<< When I set the database Connected property to TRUE for the third
database, connected to the third session, I get the "#300: cannot lock the
database for shared access." >>

See here:

http://www.elevatesoft.com/supportfaq?action=view&category=edb&question=cannot_lock_database

--
Tim Young
Elevate Software
www.elevatesoft.com