What BDEChecker does

BDEChecker performs a number of tests on your machine. These tests check various settings on your machine. These are settings that are known/believed to cause problems with Paradox data tables.

Typically you would put the program on a floppy disk or on some common network folder. There is no install program, just run it as it is. It is assumed each machine will already have a copy of the BDE on it. Then at each machine on your network, run this program. It is important that every machine on the network is checked. It only takes one rogue machine on a network to cause paradox data corruption.

To run the checks, start BDEChecker and then press the run button. A report on the checks run and the results should appear in the main window. You can print this or copy it to the clipboard and paste it into another program (e.g. A word document or an email program).

On Windows95/98/ME Systems

The program first checks some Windows systems DLLs (vredir.vxd & vnsetup.vxd). Older versions of these were known to cause problems. It also checks some registry settings relating to these services.

Then a number of registry sessions are checked relating to disk/file caching.

The program also checks some Novell Netware settings. These can be ignored if Netware is not being used.

On WindowsNT/2000/XP Systems

BDEChecker checks the registry to ensure that Opportunistic Locking has been disabled. The location of these settings is slightly different between NT & 2000.

The BDE

The program first checks the version number of the BDE. It issues a warning if the version number is older than the current version (version 5.2.0.2).

The program also notes the location of the .net file & the private folder. The .net file should be the same for all machines on the network.

Lastly the BDEChecker checks the setting of LOCAL SHARE. It should be set to true. This is the most important setting of all. Don't even consider setting it to any other value!