Hello, Paul, Alan!

PV> "Windows Embedded now contains a SuperClassic instead of a SuperServer engine.
PV> File locks are shared, so a database can be accessed by one or more Embedded
PV> servers and a regular Classic or SuperClassic server at the same time.
PV> Consult the Firebird 2.5 Release Notes for full details."

Yes, but this provocates some people to use embedded for multi-tier
middleware, where definitely server (not embedded) must be used.

AM> It appears that updates from one process are visible to the other(s) but I'm
AM> not sure how the second would know if a transaction is being managedin the
AM> first - is there a lock file being written to somewhere that I can't find?

I need to note that Embedded Firebird is a dll that works in an
address space of it's caller (exe). Thus EXE itself becomes "server".
And if that "server" have bugs, chances to get broken database are much
higher, especially if you want to use multiple exe+embedded on one DB.

--
Dmitry Kuzmenko, www.ib-aid.com