Subject | Re: [IBO] configuring IBO 4.3Aa for FB 1.5 |
---|---|
Author | russellbelding |
Post date | 2004-05-14T22:17:40Z |
Thanks constantijnw and Daniel
In summary, for a package like mine using
IBO4.3Aa +
FB 1.5 +
GDS32.DLL in the same directory as the executables
making the transition from FB 1.0.3 to FB 1.5 requires only
replacing the older GDS32.dll with a FB1.5 GDS32.dll made with
insclient.exe. (discussed in the excellent FB release notes)
Nothing needs to be done with firebird.msg vs interbase.msg as the
error messages are handled first by the FB server and feed to client
apps by IBO.
Regards
Russell Belding
In summary, for a package like mine using
IBO4.3Aa +
FB 1.5 +
GDS32.DLL in the same directory as the executables
making the transition from FB 1.0.3 to FB 1.5 requires only
replacing the older GDS32.dll with a FB1.5 GDS32.dll made with
insclient.exe. (discussed in the excellent FB release notes)
Nothing needs to be done with firebird.msg vs interbase.msg as the
error messages are handled first by the FB server and feed to client
apps by IBO.
Regards
Russell Belding
--- In IBObjects@yahoogroups.com, Daniel Rail <daniel@a...> wrote:
> Hi,
>
> At May 14, 2004, 05:58, constantijnw wrote:
> > Correct. IBO looks for gds32.dll. A lot of apps/comps
(called "legacy"
> > apps in English?) have hard-coded this name, and therefore Fb 1.5
has
> > included a SPECIAL gds32.dll which only redirects calls to
> > fbclient.dll.
>
> The gds32.dll that you refer to here no longer exists. There were
> problems in some version of Windows. Now, there is a special
> instclient.exe that can be run to rename fbclient.dll to gds32.dll
> and change the version number from 1.5 to 6.3, so that it would work
> with the latest IBX versions from Borland. If only using IBO, then
> just renaming fbclient.dll to gds32.dll is enough.
>
> --
> Best regards,
> Daniel Rail
> Senior System Engineer
> ACCRA Group Inc. (www.accra.ca)
> ACCRA Med Software Inc. (www.filopto.com)