Part 3: The 32-Bit Drivers : The dBASE Driver : Connection Option Descriptions : Lock Compatibility

Lock Compatibility
Attribute
LockCompatibility (LCOMP)
Purpose
The locking scheme the driver uses when locking records.
Valid Values
Clipper | dBASE | Fox | Q+E | Q+EVirtual
The advantage of using a Q+E locking scheme over dBASE locking is that, on Inserts and Updates, Q+E locks only individual index tags, while dBASE locks the entire index. The following values determine locking support as described:
If you are accessing a table with an application that uses the dBASE driver, your locking scheme does not have to match the Create Type. If you access a table with two applications, however, and only one uses the dBASE driver, set your locking scheme to match the other application. For example, you do not have to set this value to Fox to work with a FoxPro table. But if you are using a FoxPro application simultaneously with an application using the dBASE driver on the same set of tables, set this value to Fox to ensure that your data does not become corrupted.
Default
dBASE
GUI tab
Advanced tab[dBASE]
Advanced tab [FoxPro]

© 2013 Progress Software Corporation and/or its subsidiaries or affiliates.