We have an old application that uses BDE to connect to SQLServer database,
an the following error occurs in some (not all) machines that have the
application installed:
"An error occurred while attempting to initialize the Borland Database
Engine (error $2109)"
This error occurs when we run the application for the first time, but by
shutting down the application and then run a second time, the error doesn't
occur and the application works just fine.
Another example of this error is when we open the BDE Administrator Console,
and then tried to run the application the error also occurs. This situation
occurs in some machines.
Is the problem any kind of configuration in the machine where the error
occurs?
How can I solve this problem?
Thanks
--
Bill Todd (TeamB)
I suspect that the problem is about some kind of lock system
that appens when loading the DLL, but why only occurs in some
machines?
Can you tell me how can I find what is preventing the DLL from
loading?
Thanks
> Can you tell me how can I find what is preventing the DLL from
> loading?
Sorry no. The firs thing I would look at is the permissions on the BDE
directory and the files in the directory to see there is an access
rights problem.
--
Bill Todd (TeamB)
There is a FAQ on this subject.
http://www.inprise.com/devsupport/delphi/qanda/1323.html
In addition to what is reported there, I think that I got that message
when I had forgotten to specify a location for the NET DIR paramater in
the BDE Administrator.
See the following document for lots of good information about the BDE.
http://www.inprise.com/devsupport/bde/ti_list/TI2770.html
Specifically, this entry
TI2817 Understanding the PARADOX.NET file with the BDE
deals with setting the "NET DIR" parameter.
mIKE
'$2109 Cannot initalize the BDE' error when deploying InstallShield
application
Question:
I get error $2109 "Cannot initalize the Borland Database Engine"
when running an application deployed with
InstallShield Express. What's wrong?
Answer:
A problem with either ISExpress or your setup configuration in
ISExpress has caused the following entry to be left out of the
registry:
HKEY_LOCAL_MACHINE\SOFTWARE|BORLAND|DATABASE ENGINE | DLLPATH.
This entry is probably empty on the deployed machine's registry.
Enter the path to IDAPI32.DLL (usually \borland\common files\bde)
<ei0...@student.estg.ipleiria.pt> wrote in message
news:45c08a9d$1...@newsgroups.borland.com...