>Thanks for that. Do you happen to know if this will drastically slow the system down? I'm sure I need to do it to ensure that transaction processing is correct. Do you have any views on this?

I believe it is even more important to disable lock status and/or data caching in the network redirectors at both server and workstations: http://support.microsoft.com/kb/q129202/

As you can see, most of the default settings are for "performance" rather than "safety". I don't know of anyone who has studied the impact on speed with VFP. I did run into one non-VFP circumstance where turning off opportunistic locking greatly reduced performance: FYI: NT/W2K Opportunistic Locking Thread #462793 Message #462793

These days, disk caching in W2K/XP etc. is pretty solid. Turning it off at server and WS is probably the absolute safest thing to do but it will affect every app on both the local WS and the server, especially any that are disk-bound.

If transaction integrity is absolutely crucial to you, you're probably better off using a dedicated backend database like SQL Server. Transactions in VFP are inherently less safe because they are implemented at the workstations where they can be affected by power fluctuations, crashes/freezes, network glitches etc.