:: What you suggest may arguably be a good idea, but you need to
:: understand that the model you are proposing is not how
:: embedded works.

I understand that's not how it works now. Im proposing a new embedded
option. :)

:: So why use embedded? There are a number of places where it is really
:: useful. For example, you may have a simple stand alone application
:: where you need a DB backend but you do not want to have to install
:: Firebird or interfere with other Firebird or Interbase installations

Yes of course, but consider multiple applications wanting to use the same DB
as well, or even multiple instances of the same application.

:: installing a database. (not that installing FB is a particularily
:: labourious task, but it is always easier to dump a few dlls in the
:: applications folder. Yet another example is if you want to release

That's not the issue. The issue is that it has "interference" from firewalls
and other such items. Noone seems to haven answered how I can solve the
firewall (Access in local mode, without needing it using a TCP port) nor how
I can even detect if FB is running to start an instance.