The LockFiles setting uses record locking to force systems to not cache any information from a file by locking and/or verifying the current data file or record.
It also can verify each new record that is written. Keystroke toggles the record lock setting whenever a file is opened (on most networks this will cause any caches to be flushed). It can also be set to lock each new record and the header record when new records are being added.
Has the same effect as the LockFiles= startup switch.
LockFiles accepts the following values:
0 - Do not lock or verify files or records.
1 - Lock/Unlock file when opened.
2 - Lock/Unlock records when adding new records (i.e. database records or transactions).
3 - (2+1) Lock/Unlock files when opened and Lock/Unlock records when adding new records.
4 - Verify each new record. This setting forces Keystroke to read back the header record and the new record that was just written to make sure they are the same (it will toggle the record locks at this point also if set to do so). Keystroke will try up to 20 times to rewrite a record if it is unable to verify it.
5 - (4+1) Will verify each new record, and Lock/Unlock files when opened.
6 - (4+2) Will verify each new record, and Lock/Unlock records when adding new records.
7 - (4+2+1) Will verify each new record, Lock/Unlock files when opened, and Lock/Unlock files when adding new records.
Note: These settings (especially 4-Verify) slow Keystroke down and are designed to be used in environments with chronic file corruption problems. In almost every case of unexplained data errors, bad power is the cause. The solution is to install good UPS's (Uninterruptible Power Supply) and/or Line Conditioners with voltage regulation on every computer.