Subject | IB_SQL wants client DLL in Windows\System, correct? |
---|---|
Author | davidlhoffman66 |
Post date | 2007-02-26T19:00:38Z |
Hi, I know the location of fbclient.dll (and gds32.dll) have been
discussed a million times, and this isn't a show-stopper. I'm just
trying to make sure I understand (and follow) current best practices.
The FB2 release notes make a pretty strong case for keeping
fbclient.dll out of the windows\system32 directory ("we would be
creating our own DLL hell if we continued the practice of using the
system directory for the client library").
As near as I can tell, system32 is where the latest version of IB_SQL
(V4.7_Build16) utility wants it, otherwise "Firebird/Interbase Client
DLL is not installed."
I'm mainly trying to avoid multiple copies of fbclient.dll from being
sprinkled around. Is there a way to tell IB_SQL to look in the bin
folder of the FB DefaultInstance for the client DLL?
Thanks-
-David
discussed a million times, and this isn't a show-stopper. I'm just
trying to make sure I understand (and follow) current best practices.
The FB2 release notes make a pretty strong case for keeping
fbclient.dll out of the windows\system32 directory ("we would be
creating our own DLL hell if we continued the practice of using the
system directory for the client library").
As near as I can tell, system32 is where the latest version of IB_SQL
(V4.7_Build16) utility wants it, otherwise "Firebird/Interbase Client
DLL is not installed."
I'm mainly trying to avoid multiple copies of fbclient.dll from being
sprinkled around. Is there a way to tell IB_SQL to look in the bin
folder of the FB DefaultInstance for the client DLL?
Thanks-
-David