Elmar,

>> But I'd have to install Classic separately from my app, wouldn't I? I
>> couldn't just include a DLL with my app like I do with embeddeded,
>> right? Basically, I'm looking for a "no setup" method... this is a
>> freeware app, so I need it light and simple to install.

EH> Since you have your App running as a service, it certainly is not an
EH> Copy-Only Install. I'm shure that you can extend your Installer to
EH> create the FB services (DB-SErver and perhaps guardian service) also.

it is less intrusive and more effective to launch the Firebird server
as an application from your service, instead (this allows you to set
the FIREBIRD environment variable in the CreateProcess call as well).
If you insist on installing it as a service, then you're not going to
be able to use the provided instsvc tool, since it hard-wires the
service name. As you know no two services with the same name (or even
display name) can coexist on a given machine. If you succeed in
installing it as a service without blocking another installed
instance, you're going to have problems with the home, since both
instances will look in the same path. All in all, Firebird is
currently not ready for multi-instance installations, so a private
copy launched as an application is the best path.

Ciao
--
Nando Dessena
http://www.flamerobin.org