Using Paradox tables

Notes to be aware:

When you are sharing Paradox tables over a peer-to-peer network (in NT servers as well), be sure to turn on the LOCAL SHARE flag in the BDE Administrator configuration page.
To minimize database corruption, call DbiUseIdle in the Application.OnIdle event. The DbiUseIdle function is declared in the BDE unit.
Minimize the usage of secondary indexes. They tend to corrupt easily when they are large. Only use them for performance reasons.
When using Paradox tables, I strongly recommend download RxLib. It is an excellent package with a component called RxQuery and RxQBE. The latter one offers much faster performance when you do queries with Paradox tables compared to SQL, especially when you have large master/detail joins. However, using QBE will make porting your application to SQL servers more difficult later.
If you plan to upsize your database to a client/server based later, avoid using TTables at all cost. They are only good for ISAM databases like dBASE or Paradox but perform terribly in SQL servers.