If your application is creating PARADOX.LCK and PDOXUSRS.LCK files, it is also creating or accessing a PDOXUSRS.NET file somewhere.
The BDE uses a single common PDOXUSRS.NET file, and a PARADOX.LCK and PDOXUSRS.LCK file in each shared directory, to coordinate shared access among the distributed instances of the engine.
You must find out if your application shares the tables with any other application. If the data is shared, you must allow the BDE to create and use these lock files.
If you are certain that you are the SOLE user of the data, you can eliminate the creation of the lock files. But -- unless the lock files are the only thing preventing you from doing something useful, it is rarely worth blocking their creation.
Registry entries tell the BDE where to find its configuration file. A configuration file editor ships with the BDE; look for BDEADMIN.EXE or BDECFG32.EXE. The configuration editor uses the same registry entry to determine which file to edit.
To avoid creating lock files when you are the sole user of the data:
Open the config editor.
Go to Configuration | Drivers | native | PARADOX, or Drivers | PARADOX, and note the NET DIR entry.
Set the NET DIR value to blank.
Go to Configuration | System | INIT, or System, and set LOCAL SHARE to False.
Save your edits.
Follow the path you noted in step 2 and delete the PDOXUSRS.NET found there.
Delete any leftover PARADOX.LCK or PDOXUSRS.LCK files in your data directory.
Warning: fooling around with the lock files when you don't understand their purpose is a good way to brick your app.
-Al.