Subject | Simultaneous IB and FB install with ODBC |
---|---|
Author | Jarrod Hollingworth |
Post date | 2004-02-17T23:46:35Z |
Is there any way to get an ADO->ODBC connection to a FB database to work
while an old IB gds32.dll is in the Windows system directory?
Our Delphi app uses a direct IBO connection to one FB database and an
ADO->ODBC connection (using the IBPhoenix Firebird ODBC driver) to another
FB database. To support other applications IB must still be installed with
the IB gds32.dll in the Windows system directory.
For direct connectivity to the first FB database placing the FB gds32.dll in
the application directory is sufficient. For the ADO->ODBC connection we
can't stop it from using the gds32.dll in the Windows system directory and
the application cannot connect to the second database (it hard crashes in
fact with a "Send report to MS..." dialog in WinXP).
Perhaps if the ODBC driver were to use fbclient.dll directly then all would
be ok?
Any ideas?
Regards,
Jarrod Hollingworth
Backslash
while an old IB gds32.dll is in the Windows system directory?
Our Delphi app uses a direct IBO connection to one FB database and an
ADO->ODBC connection (using the IBPhoenix Firebird ODBC driver) to another
FB database. To support other applications IB must still be installed with
the IB gds32.dll in the Windows system directory.
For direct connectivity to the first FB database placing the FB gds32.dll in
the application directory is sufficient. For the ADO->ODBC connection we
can't stop it from using the gds32.dll in the Windows system directory and
the application cannot connect to the second database (it hard crashes in
fact with a "Send report to MS..." dialog in WinXP).
Perhaps if the ODBC driver were to use fbclient.dll directly then all would
be ok?
Any ideas?
Regards,
Jarrod Hollingworth
Backslash