Subject | Re: [firebird-support] Embedded Firebird Libary using Firebird-Server |
---|---|
Author | Martijn Tonies |
Post date | 2004-05-13T13:01:58Z |
Hi,
Already thought of a multi-instance install?
You can install Fb 1.5 and use it on a different port -
next, install the client in your apps dir so that remote
clients will use the right version of "fbclient.dll".
Make sure to connect to your own remote Firebird
service.
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com
Already thought of a multi-instance install?
You can install Fb 1.5 and use it on a different port -
next, install the client in your apps dir so that remote
clients will use the right version of "fbclient.dll".
Make sure to connect to your own remote Firebird
service.
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com
>we
> we have an application using firebird. In the past we used V1.03 but now
> want to switch to V1.5 final. We only support Windows (clients andserver).
>running
> The problem is, that we have an (increasing) amount of errors/problems
> regarding to other applications that are also using the firebird/interbase
> server. Some of them use different versions of the server, some are
> with a local server installation, some use modified sysdba-passwords,....In
> addition we do not install our app - our customers do that (and they arefar
> away from being "computer-freaks"). Last but not least our software can bebe
> used single- or multiuser - with or without a dedicated server.
>
> While testing multiple situations I got the idea that I could use the
> embedded Server to solve my problems.
>
> Idea:
> - Our setup always installs a complete embedded server (renamed to
> gds32.dll, intl-dir, firebird.msg,...) in the application's directory.
> - If the user decides to have multiuser-access the FB-Superserver will
> installed (additionally). In this case our emedded-server-dll acts as awill
> simple, "normal" system32\gds32.dll. The database will be accessed via
> TCP/IP.
> - If the user decides to have single-user-access only, we don't need to
> install the Superserver - we'll use the embedded server. The databases
> be accessed via the local-protocoll.does
>
> Advantages (in theory):
> - No other Firebird/Interbase installation (at least at the client
> computer) can "disturb" our app.
> - No chance of mismatch between gds32.dll and the messages-file.
> - We don't need to run the firebird "clientsetup" on every client.
> - ...
>
>
> I did some tests with different combinations and it seems to work. But I'm
> afraid that this was pure chance.
>
> Does anybody know if this should work under all possible conditions or
> anybody know that it could/should fail? What about Win98 (a lot of our
> customers still use it)?