Subject | Re: [firebird-support] Re: FBClient.dll and legacy gds32.dll |
---|---|
Author | Helen Borrie |
Post date | 2004-05-08T23:10:15Z |
At 10:52 PM 8/05/2004 +0000, you wrote:
actually got written. (The build version string should have the same build
number as the server executable). The reason is, if you had an old
gds32.dll there and the install script detects either Firebird 1 or an IB
installation in the Registry, it won't write its own gds32.dll to
system32. Another condition under which it might not get written is when
there is already a gds32.dll loaded - in that case Windows won't let it be
overwritten.
/heLen
>In the FB1.5 client install, the option to include a copy of theOK, check the build version string of this gds32.dll to make sure it
>fbclient dll as gds32.dll is "Generate client library for legacy apps?
>I should have referred to the "legacy app gds32.dll". Sorry for the
>misspeak and thank you for explaining the path issue.
actually got written. (The build version string should have the same build
number as the server executable). The reason is, if you had an old
gds32.dll there and the install script detects either Firebird 1 or an IB
installation in the Registry, it won't write its own gds32.dll to
system32. Another condition under which it might not get written is when
there is already a gds32.dll loaded - in that case Windows won't let it be
overwritten.
/heLen