Jason Dodson wrote:

> I think you need to reread this sentence:
>
> "Yes, but only the first instance will get access to the database if
> you both applications to access the same database."
>
> What you want to do is have two applications have a delegator to a single embedded connection to the database. An
> ActiveX server would be a perfect solution... and you can expose your own api to your applications.
>
> Jason
>

Well.Embedded is just a superserver engine plus client inside single
DLL.What I'm asking is:
- when first application loads fbembed.dll into memory and open
connection to database, creating locks and so on
- when second application load fbembed.dll it creates second superserver
engine or just use that created previously ? (in later case it should work)


I think that it's not so obvious that's why I want to be sure.


Regards
Boguslaw