1
votes

I am working with Paradox table using BDE engine. Lately, we are simply running into all kinds of problem trying to install BDE engine - Out of space, Error Copying BLW32.dll file, on and on. However, if you keep trying it eventually installs.

I am seriously thinking about moving away from BDE Engine all together. So, I would like to know what is out there that will work with Paradox table.

2
Probably not what you want to hear, but when I ran into a similar issue a few years back, I solved it by converting the whole thing to a Firebird database. ;)Mason Wheeler
Paradox was a great idea in 1998. Not a great idea anymore. Besides Firebird, you may also want to consider SqLite, PostGres, and MySql.Warren P
@WarrenP - More like in 1988! I think the only time I used in was in 1990.Gerry Coll
I didn't learn to embrace SQL databases until about 2008. I'm a late bloomer.Warren P
What Delphi version are you using now?Jan Doggen

2 Answers

2
votes

Maybe this will help you:

http://support.microsoft.com/kb/326548/en-us

It's about the Jet OLE-DB provider that, acording to this paper, is able to open Paradox 5 files. I'm not sure what Paradox version BDE uses but it's worth a try.

You will have to use TADOTable and TADOQuery components.

Get rid of BDE as soon as you can!

0
votes

As all of you have suggested and commented, I totally agree that install for BDE Engine on latest windows is very very buggy. However, I believe that its installation is the one that seems to be having problem not the BDE Engine itself.

As suggested by other question in Stackoverflow, I came to a conclusion that I should be able to take the extracted files from common\bde folder and link them to my software install. So, that whenever I install my software, BDE Engine files also get transferred into its folder on C drive. That it does. Also, I have created the registry file to update the registry accordingly for the BDE. It is mainly located in HKEY_LOCAL_MACHINE\software\Borland. To create the registry file, just right click on the folder and choose "Export" option. I shellexecute the registry file as part of the installation process.

It all works without any problem. Now, I don't have to deal with all these errors. My software is up and running. For now this is a quick fix but definitely going to get rid of it in the next revision.