Shaq,
as per my previous post on this subject:

Re: [IBO] Client library mystery (rewritten)

To force your app to use the fbclient.dll in your application's path,
create an empty file of the same name as the exe, with a .local
extension. eg:
MyApp.exe
MyApp.exe.local

From memory, win2k+ may not look at the local application path first to
load libraries...it has some other weird and wonderous path it takes
(particularly if the dll is setup as a shared DLL).
Reference:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsetup/html/dlldanger1.asp
http://home.att.net/~raffles1/dll_loading_rules_in_win32.htm


cheers
Mark

Shaq wrote:

>I also found that fbclient.dll is not called if it is not located in
>the same directory. I do have it in the system32 directory of my
>machine. It should find it there right?
>
>-Shaq
>
>--- In IBObjects@yahoogroups.com, "Shaq" <shaq@b...> wrote:
>
>
>>If I just have the IB_Components in my uses class with no other
>>components, I find that my application calls fbclient.dll. I tested
>>with a brand new project and just added IB_Components to my uses list.
>>
>>I also had the fbclient.dll in the same directory as the exe if that
>>makes a difference or not.
>>
>>I am just wondering why this is happening.
>>
>>-Shaq
>>
>>
>
>
>
>