Helen,

Thanks for responding.

I've been doing some more experimentation, but still no joy on Win98.

Yes, Msvcp60.dll is installed. Tried it in both \Windows and
\Windows\System.

Although the FB 1.5 release docs clearly state that FBCLIENT.DLL is
the new client library and GDS32.DLL is no longer needed, I believe
that a "legacy" app like IBO is still looking for GDS32.DLL
(Jason?). I tested this on my WinXP Pro box by renaming GDS32.DLL
to FBCLIENT.DLL. The app now fails. Changed it back to GDS32.DLL
and it works.

Here's something from the FB 1.5 RC7 README_library_install.txt file:

Now the client library is named "fbclient.dll". To provide a
compatibility with existing applications, a gateway
library "gds32.dll" is included in the distribution kit. This library
doesn't have any code but just redirects all calls to fbclient.dll.
Hence for old applications you must to have both fbclient.dll and
gds32.dll in the program directory or OS system directory. It's
recommended to use native fbclient.dll library in newly developed
applications. All server utilities (gbak, gfix, etc) uses only
fbclient.dll and do not require gds32.dll.

Also from the same readme file:

A new registry key has been added and all Firebird compliant
applications must now use this to locate the correct version of
Firebird that they wish to use. The new key is:

HKEY_LOCAL_MACHINE\SOFTWARE\Firebird Project\Firebird
Server\Instances

Firebird will guarantee that one entry under this key always exists.
It will be known as "DefaultInstance" and will store the path to the
root directory of (yes, you've guessed it) the default installation.
Those that don't care about particular installations can alway use
the default instance to locate the fbclient.dll.

Helen, I've done all the above, but no joy. FWIW - I have not
installed FB itself on this Win98 box. Don't need it - my FB DB is
on my RH9 box. Also, I'm using IBObjects 4.2b.

Any other ideas? Anyone else having this same problem?