Hello,

>> So, what are your alternatives? Either superserver or classic -

W> both

>> handle multiple connections. They've got a bit more overhead than
>> embedded - an environmental variable to define, and a service or
>> application to start in the case of superserver. However, neither

W> takes

>> much memory and both are reasonably small on disk.

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

You *can* install a private copy of the Firebird server together with
your application, as Ann has hinted. For SS, you need to make sure
that CreateInternalWindow is set to 0 in the config file, that the
server listens on a free TCP port and that you launch it (as an
application, not as a service) with the FIREBIRD variable defined.
This is enough to avoit colliding with other instances of Firebird on
the machine. See the docs.

Ciao
--
Nando Dessena
http://www.flamerobin.org
======================================================
I support Firebird, I am a Firebird Foundation member!
Join today at http://www.firebirdsql.org/ff/foundation
======================================================