BDE admin. 5.01 configuration for Oracle
Dino Hsu
When connecting to Oracle database through BDE (Borland database
engine) admin. 5.01, I know from experience the following settings
should be changed: (under configuration->drivers->native->ORACLE)
1.DLL32: from SQLORA32.DLL to SQLORA8.DLL
2.VENDOR INIT: from ORA73.DLL to OCI.DLL
If we don't change them, the connection will fail with the following
errors:
a.Windows 98: Cannot load an IDAPI service library
b.Windows 2K: vendor init error
I have tried these:
a.Oracle 8 client or Oracle 8i client
b.install Oracle client before or after BDE
Anyone knows why these changes are necessary? Thanks in advance.
Dino
Nicolas Bronke
> engine) admin. 5.01, I know from experience the following settings
> should be changed: (under configuration->drivers->native->ORACLE)
> 1.DLL32: from SQLORA32.DLL to SQLORA8.DLL
With sqlora8 there have to be several entries to be changed, also you need
the newest sqlora8.dll
May be you should also download the latest BDE update (although it should
work with this release)
> 2.VENDOR INIT: from ORA73.DLL to OCI.DLL
> If we don't change them, the connection will fail with the following
> errors:
> a.Windows 98: Cannot load an IDAPI service library
> b.Windows 2K: vendor init error
Did you reboot? Are the path correct?
Some more details to your database configuration would helpful.
Also:
forums.inprise.com and there the newsgroup borland.publuc.bde
Regards
Nicolas
Dino Hsu
wrote:
This problem has lasted for a long time (about 2 years), especially
with Oracle 8.0.5 + Windows 98 + BDE 5.01, I have encountered it so
many times that I cannot deny the fact. I just found this happens with
Oracle 8.1.7 client and/or Windows 2K as well, so I asked.
If you mean the re-boot after the Oracle installation which makes PATH
environment variable effective, I am very sure of it, because Oracle
was installed a while ago before BDE was installed with Borland C++.
Dino