John,

Look at using the CURVAL(), OLDVAL() functions to test for changes made by other users. Also use GETNEXTMODIFIED() to go record by record and test conflicts there. There is a decent example of this in the VFP documentation for multi-user issues (I forget where exactly).

> I am using native table buggering - 5 in my multiuser application.
> My table (customer) consists of 10 fields. I allow user to keyin, update and etc customer details in my customer form. There are 7 fields only which are allowed to be updated only shown in customer form. The others 3 fields will not be shown (used for other accumalate purposes).
> I got a Error - Update conflict when my application update. The steps to reproduce are as the following:
>
>1. User A search for customer details and update certain updatable fields
>2. Before user press "save" button to save changes, that was a changes by other user for that 3 fields for accumalate purposes.
>3. When User A press "Save" to sace changes, VFP return update conflict.
>
>Any way to have same featuce of view (DB_KEYANDMODIFIED )? Since my application only REPLACE 7 fields instead of 10, how to prevent update conflict and "order"
>VFP just check conflict for that 7 fields instead of 10??
>
>Thank you