Subject | Re: [IBO] IBO components and Embedded FB |
---|---|
Author | Helen Borrie |
Post date | 2006-01-22T21:54:03Z |
At 07:09 AM 23/01/2006, you wrote:
replace the value for the variable IB_GDS32 in ib_constants.pas, you
would need to rename fbembed.dll to gds32.dll. However, this isn't a
perfect solution, as you may come to grief with the Service
components or the command-line utilities (one or both).
If you're not aiming for InterBase compatibility for your server
deployments, my preference here is to fix up your project sources so
*everything* looks for a client named fbclient.dll. That way, none
of your deployments will trip over the risk that a
Borland-distributed gds32.dll of unknown version is lurking somewhere
in a path where the IBO app will find it first.
I note you're also posting Delphi-related questions in the
firebird-support list, regarding use of the Classic server. If you
are planning to deploy your IBO app[s] for use with either
Superserver, Classic or Embedded, you should definitely go the route
of eliminating 'gds32.dll' from everything AND of externalising the
Server, Protocol and Path properties to an ini file or Registry entry
and, in the case of Path, using an alias.
Helen
>HiUnless you have modified the IBO sources (or your project source) to
>
>I am creating an app that will run with FB embedded. Some of the
>machines it will run on will also be running full FB. Am I right in
>saying I just need to do the following...
>
>Use a Local connection instead of TCP/IP
>Install FB Embeded into the same dir as app and rename |fbembed.dll to
>|fbclient.dll.
>
>Are there other steps required?
replace the value for the variable IB_GDS32 in ib_constants.pas, you
would need to rename fbembed.dll to gds32.dll. However, this isn't a
perfect solution, as you may come to grief with the Service
components or the command-line utilities (one or both).
If you're not aiming for InterBase compatibility for your server
deployments, my preference here is to fix up your project sources so
*everything* looks for a client named fbclient.dll. That way, none
of your deployments will trip over the risk that a
Borland-distributed gds32.dll of unknown version is lurking somewhere
in a path where the IBO app will find it first.
I note you're also posting Delphi-related questions in the
firebird-support list, regarding use of the Classic server. If you
are planning to deploy your IBO app[s] for use with either
Superserver, Classic or Embedded, you should definitely go the route
of eliminating 'gds32.dll' from everything AND of externalising the
Server, Protocol and Path properties to an ini file or Registry entry
and, in the case of Path, using an alias.
Helen