At 07:18 PM 24-01-02 +0100, gerhard wrote:

>hi lou,
>i also not understanded really, what this means.
>Normalley the gds32.dll is under p.e.: c:\winnt\sytem32 ...
>but if you have your gds32.dll under p.e.: d:\program files\Borland\Interbase\bin,
>you should define a path-variable in NT control panel, system ...
>so i think ...

You do misunderstand. gds32.dll is not the server, it is the client. A remote client does not need the INTERBASE variable. A path to gds32.dll is not required, since the system directory is in the Windows default path.

>I deleted the older gds32.dll in system32, and have only the FB RC2 gds32.dll in the interbase\bin directory.

You shouldn't have gds32.dll in the interbase\bin directory. In fact, you should not have an interbase\bin directory.

>then i edited the Path - Systemenvironment variable ....
>thats all ...
>
>the reason for this changing (new home of gds32.dll) i don't know, sorry ...
>perhaps i made something wrong, but it works:)

I guess it works because you are working with a local client, only. The exe's path is also in the Windows default path - it is "first stop" and the system directory is the "second stop". You don't have to set the Windows default path. You can't override it, either.

The default path thing has caused problems in the past for IBConsole users who moved gds32.dll from their old Borland Interbase distro into the same directory as the IBC executable. When they use IBConsole, they use the wrong gds32.dll because Windows finds it first.

regards
helen

All for Open and Open for All
Firebird Open SQL Database · http://firebirdsql.org
_______________________________________________________