:: they can't use the same instance of the dll - so no
:: But if you had a middle tier using the embedded and both
:: apps connected to
:: this tier - then yes. The middle tier would be loading one
:: instance of the
:: embedded dll and making as many connections as it wishes to
:: that one DB. But

Actually they are all calling into a core assembly. But the assembly is
loaded by mulitple applications, so it would depend how the DLL handles
things internally. But it sounds like it uses thread communication and not
IPC.

What I'll likely have to do is run embedded for the demo and install server
for beyond demo.

If I want to install a server on the users computer - any articles or tips
on what I have to install? Id like to install it directly as part of my
install, not to call out to another install. These users really don't care
about the DB, and in fact wont want to mess with it. Once its in automatic
though I can say its FB, but they wont want to "mess" with it, this will
turn them off.