Josh,

Like James, I, too, have been confused by these "options" and learning EXACTLY what they do.

You seem to have a real good handle on this. Can you share where you got this information?

Cheers,

Jim N

>Actually, all of the fields you set to update will be updated regardless of the setting for SQL WHERE CLAUSE. This setting effects how VFP determines whether a record has changed since the user started editing it. When you use Key Fields Only, VFP will update the record as long as the key field hasn't changed. If you use key and modified fields it will update as long as the key and any fields the user modified weren't changed by another user. Key and modifiable fields does the same thing but checks all fields that you set as updatable whether the user changed them or not.
>
>The fewer fields in the WHERE clause the faster the update. However, if you don't want to overwrite another user's changes, you'll need to use option 2 or 3. Of course, if you use the force parameter in TABLEUPDATE(), the update will occur regardless of whether another user made changes.
>
>>James ---
>>
>>>I am designing local views and I am not sure that I understand what is meant by the SQL WHERE CLAUSE. The default selection seems to be 1 (Key fields only).
>>>
>>>If I want both key fiends and modified fields to be updated, shouldn't I select option 3 (Key and modified Fields)?
>>>
>>
>>Absolutely.