Subject | Re: Evaluation of Firebird 1.5 as a replacement of BDE+Paradox |
---|---|
Author | Adam |
Post date | 2006-09-12T12:22:22Z |
--- In firebird-support@yahoogroups.com, "gerardusmercator"
<gerardusmercator@...> wrote:
you are that way inclined. Otherwise just execute the installer.
only a new instance under the classic architecture. Under Superserver,
it is just a new thread.
Adam
<gerardusmercator@...> wrote:
>LOL. It is much less problematic than BDE + Paradox
> Hi all.
>
> I am evaluating Firebird 1.5 as a replacement of the BDE + Paradox.
> I have some doubts about the deployment of the Firebird server:
> - Is there a way to embed the installation of the FB 1.5Yes, the source for the installer is available for you to duplicate if
> classic/superserver in one's own app install process?
you are that way inclined. Otherwise just execute the installer.
> - What if my app installs a FB 1.5 classic or superserver on aThey can work together but only on different ports (obviously).
> computer that already has a FB 1.0 or Interbase server (6.X or later)
> installed. Will it interfere with the other servers installations or
> can they work simultaneously?
>It would make a new connection to the database server yes. That is
> Currently, the app has an Excel add-on (a DLL wrapped by a XLA, may be
> converted to a XLL soon) that accesses the DB directly.
> This wouldn't be possible with an embedded server, as the Excel add-on
> would load another instance of the server, right?
only a new instance under the classic architecture. Under Superserver,
it is just a new thread.
Adam