Running the Borland Database Engine (BDE) on Windows 10 and 11

If a program has told you it needs the Borland Database Engine, or it has stopped working after a Windows upgrade or a move to a new PC, you’re not alone. A great many business applications written in Delphi in the 1990s and 2000s depend on BDE, including off-the-shelf packages for medical practices, manufacturers, membership organisations and trade businesses. Many are still in daily use.

What BDE is

The Borland Database Engine is the layer that lets these applications read and write their data, most often Paradox or dBase tables stored as files on a PC or network share. The application talks to BDE, and BDE talks to the files.

BDE was deprecated many years ago and hasn’t been developed since. It still works on Windows 10 and 11 in most cases, but it was designed for a world of single machines and simple networks, and modern Windows gets in its way.

Before you change anything

Take a copy of the application folder and, most importantly, the data. Paradox tables can be damaged by a bad configuration change, and having a copy means every step below can be undone.

If the application came from a software vendor, check their support pages first. Many vendors that still ship BDE-based products publish their own installation notes, and their settings take priority over general advice.

Installing it

BDE is 32-bit software. On 64-bit Windows it installs under the 32-bit Program Files folder, and its settings live in the 32-bit part of the registry. It should be installed from the application’s own installer or a copy supplied by the vendor.

Avoid “BDE download” sites. Several rank highly in search results, and installing system components from unknown sources on a business PC is a serious security risk.

BDE Administrator won’t save settings

The BDE Administrator tool (bdeadmin.exe) is where BDE’s settings are managed. On modern Windows it usually needs to be run as administrator. Otherwise Windows may quietly redirect the changes, so they appear to save but the application never sees them.

The settings that matter most

Net Dir. When a Paradox application is shared across a network, every PC must point to the same shared network directory, where BDE keeps a control file called PDOXUSRS.NET. If PCs point to different places, you’ll see errors such as “Directory is controlled by other .NET file” or “Network initialization failed”. Getting this consistent on every machine is the single most common fix.

Local Share. When data sits on a network share used by more than one PC, this setting generally needs to be on, so that BDE manages file locking safely.

Lock files. Leftover .LCK files after a crash can stop the application opening. They should only be removed when everyone is out of the application.

Common errors

“An error occurred while attempting to initialize the Borland Database Engine” (often error $2109). Usually a configuration or permissions problem: BDE can’t find or read its configuration.

“Insufficient disk space” on a drive with plenty of free space. A long-standing BDE quirk in how it reads free space on large modern drives. There are workarounds, but it’s worth having someone who has seen it before apply them.

Corrupted or “damaged” Paradox tables. Often the result of network settings on modern Windows servers and PCs that cache files in ways BDE never expected. The fixes involve server and network settings, so they need care.

Keeping it running, or moving on

Most BDE problems can be fixed, and for many businesses keeping the application running for another year or two is the right decision. But BDE isn’t going to get easier to live with. Each new PC, Windows update or server change is another chance for something to break, and the people who remember how to fix it are getting harder to find.

If the application is critical, it’s worth knowing your options. Our guide to old Delphi applications covers them, including what to do if the source code has been lost.