<< Click to Display Table of Contents >> Navigation:  Application development > Locking > Locking strategy

In choosing a locking strategy, you must consider both the application's need to keep other users from changing data, and the extent to which locking affects other users. You also need to consider the differences in rules used by the lock managers of each database system being accessed. SQL lock managers use a different set of locking rules from those used by dBASE and Paradox lock managers.

Using BDE, an application can update a table as long as it has read-write access to the table, and no other user has a lock on the table or record to prevent the update. However, it is necessary with dBASE, FoxPro, Access, and Paradox systems to lock the table or record before updating to ensure that the data in the table does not change while the application is in the middle of processing a retrieved record.