:: but the embedded philosophy, if you like, is one which
:: requires a host
:: application to be running in order that the embedded server
:: start (hence a
:: dll).

Why cant they be a shared host? Ie one dll starts up, it starts up the host.
Other clietns start up, they share the host. If the first one shuts down,
the others keep the shared memory alive. I assumed that's how classic works
- but are you saying that classic has a master "Controller"?

:: Now what you are asking for would still need a host application to be
:: started (or running) for these other PCs to start using the
:: embedded server

All applications would be running on the same PC. There is no need for
network connectivity, or even file sharing of the DB over a network. Its
simple embedded, multi user, single PC, local access.

:: Cant see any other way.. unless you want to host an
:: application which starts
:: the embedded, if you create this, it's called a 3rd tier and
:: you can let as
:: many connections as like pass thru this using the embedded right now.