Subject | Firebird co-existence |
---|---|
Author | gregatacd |
Post date | 2004-12-17T21:07:29Z |
Hi all,
We are writing a set of applications for Windows that all require
shared access to a small local database. Since these are multiple
applications, we would then need to use the Firebird 1.5.1
SuperServer instead of just using the embedded engine.
If the target system already has an application that uses the
Firebird enging (same version or earlier), what is the best way to
co-exist with this? How can we (at install time) detect the presence
of an existing service? What if it's an earlier patch... do we
simply upgrade it and hope for the best?
Thx in advance,
Greg
We are writing a set of applications for Windows that all require
shared access to a small local database. Since these are multiple
applications, we would then need to use the Firebird 1.5.1
SuperServer instead of just using the embedded engine.
If the target system already has an application that uses the
Firebird enging (same version or earlier), what is the best way to
co-exist with this? How can we (at install time) detect the presence
of an existing service? What if it's an earlier patch... do we
simply upgrade it and hope for the best?
Thx in advance,
Greg