Classic server says "Several clients can open file directly". It appears
from this and other things Ive read that Classic server uses IPC mechanims
or file locks to communicate between processes.

Could not a different build of FB Embedded be made so that several
applications could use the same data file?

Here is why I want to do this. Im shipping some applications and the users
don't care what DB is used, but many are software developers. Some will
already have FB and I can have them reconfigure. But most wont have FB - and
wont want to mess with it at all. They will be ok with using FB - but not if
they have to mess with it, its install or anything. But worse yet -
installing it as a service, or even an external application will have a
"negative" effect with them. Thus I really want to use embedded as they wont
see it as external and its easy to install. There are no conflicts with
possible existing FB servers, there are no local firewall issues, etc... But
I need to have multiple clients using one database. If performance suffers a
bit, that's perfectly acceptable. These systems are not big, and for the
bigger ones they can move up to real FB server.

I cannot add another tier for all database access as that would again cause
firewall issues, and also have other impacts that are negative and not
possible.

--
Chad Z. Hower aka Kudzu
"Programming is an art form that fights back"

Still doing your website by hand? Get a free content management system:
http://www.atozed.com/iws/