>I am working on a LAN application.
>
>What is the best way to handle multiple users accessing the
>same records at once?
>

IMHO
# 3 - but let VFP handle it for you.
Use optimistic buffering - row level for tables that need one row at a time updated/reverted, table level for those that need multiple rows updated/reverted.

VFP will throw a contention error and you can trap that.

>1. Do I lock the record when the user navigates to it, therefore
>ensuring that the record is available, but keeping everyone else
>out indefinitly?
>
>2. Try to lock the record when the user starts editing, and possibly
>pop up an error message if the record in use?
>
>3. Try to lock the record when the user clicks Save, and possibly
>pop up an error message if the record in use, and forcing the user
>to either wait, or discard all the changes?
>
>4. Or, .... what eles can I do?
>
>Thanks