This one is so simple, you will wonder why you did not work it out for yourself. There are two problems with using paradox with multi-user applications, record locking and index corruption, the solutions are as follows.
To solve the record locking problem, make sure the following line of code is executed before you open any tables.
Session.NetFileDir := PathToMyData;
The second problem is caused when you use TTables to edit your data. It occurs when alterations have been made to the underlying data, and then the application is abnornally terminated (ie, power loss). The solution to this is to make sure the all alterations are written to the database immediately.
Step 1 is to include DBIProcs in your USES clause.
Step 2 is to include the following code after
Posts
Deletes
Inserts
DbiSaveChanges(MyTable.Handle);
Or you could just learn to use TQuery instead, which doesn't have the same problems.
http://sandbrooksoftware.com/DPSC/Tips/PeterMorris/tips.htm##paradox
내용은 다음과 같습니다.
Multi-user Paradox.
This one is so simple, you will wonder why you did not work it out for yourself. There are two problems with using paradox with multi-user applications, record locking and index corruption, the solutions are as follows.
To solve the record locking problem, make sure the following line of code is executed before you open any tables.
Session.NetFileDir := PathToMyData;
The second problem is caused when you use TTables to edit your data. It occurs when alterations have been made to the underlying data, and then the application is abnornally terminated (ie, power loss). The solution to this is to make sure the all alterations are written to the database immediately.
Step 1 is to include DBIProcs in your USES clause.
Step 2 is to include the following code after
Posts
Deletes
Inserts
DbiSaveChanges(MyTable.Handle);
Or you could just learn to use TQuery instead, which doesn't have the same problems.