Paradox Index Out-Of-Date

[NordicSystems]

A client uses a D3 program with Paradox database on MS NT LAN with win95 and 98 workstations. Less than 20 concurrent users at all times. Executable file and database are on server and private dirs are set to local drive in program. Problem is that the main table (orders) or its immediate 1-M child (charges) keep getting corrupt indexes - usually secondary but sometimes primary. Each table has less than 5 maintained secondary indexes and neither exceeds 50 MB table-size. Hardware all seems ok and problem not isolated to one workstation. Confusing because the .DB (and usually the .PX) file is updated fine on Post operation but one or more indexes become out-of-date. Some of the things I've tried:

1. Updated BDE version to 5.01
2. Increased file handles and buffer sizes in BDE Admin.
3. Added DBISaveRecord to AfterPost events.
4. Checked hardware and network cables.

Any ideas? Could this result from a memory conflict between the BDE and some other software?


nordicsys@aol.com

 

[mgauss]

1. be sure to close the child tables first and then the master tables
2. sometimes if a program crashes while accessing the table it will leave the Table in a n unstable state. "Improperly closing files such as due to loss of power or restarting a workstation or the server without closing files first may cause this problem. Paradox tables are not designed to withstand such behavior. If this is a possibility in your environment, we recommend you use a Client Server database that can recover from such conditions. " From borland
3.If using an NT system, diable "opportunistic locking see:

http://support.microsoft.com/support/kb/articles/Q129/2/02.asp

Hope this helps!