>
>No, I can't here but the client always have it. I just asked them to rebuild to view. It's the same situation. We really have some weird reactions of the view.
>
>I don't have a WHERE clause in the view.
>
>The following is the main definition of the view.
>
>DBSetProp('viewschedule', 'View', 'UpdateType', 1)
>DBSetProp('viewschedule', 'View', 'WhereType', 3)
>DBSetProp('viewschedule', 'View', 'FetchMemo', .T.)
>DBSetProp('viewschedule', 'View', 'SendUpdates', .T.)
>DBSetProp('viewschedule', 'View', 'UseMemoSize', 255)
>DBSetProp('viewschedule', 'View', 'FetchSize', 100)
>DBSetProp('viewschedule', 'View', 'MaxRecords', -1)
>DBSetProp('viewschedule', 'View', 'Tables', 'schedule')
>DBSetProp('viewschedule', 'View', 'Prepared', .F.)
>DBSetProp('viewschedule', 'View', 'CompareMemo', .T.)
>DBSetProp('viewschedule', 'View', 'FetchAsNeeded', .F.)
>DBSetProp('viewschedule', 'View', 'FetchSize', 100)
>DBSetProp('viewschedule', 'View', 'Comment', "")
>DBSetProp('viewschedule', 'View', 'BatchUpdateCount', 1)
>DBSetProp('viewschedule', 'View', 'ShareConnection', .F.)
>
>The key field plus 9 other fields are updatable.

I see that the wheretype is set to 3 (Key and modified fields). May be the update conflict is there. Did the client can update that view in under other conditions? If yes, maybe you should set it to 1 (key fields only). If not, the problem may be directly in the table. Does the PK in the table has a filter !Deleted() if same key?