Try changing the SQL WHERE Clause to Key fields only (I'm assuming that none of the key fields are Varchar). This may fix the problem but it means that the update will happen even if someone else has modified the record you just modified.

>Unable to update VFP5 remote view to Oracle8 VARCHAR2 column.
>
>Does the VFP remote view really support the updating of the Oracle tables? Or should the remote view be scrapped in favor of an "All SQL pass through"
>
>A similar bug was reported in the MSKB:
>Article ID: Q170129
>The information in this article applies to:
> Microsoft Visual FoxPro for Windows, versions 5.0, 5.0a
>SYMPTOMS
>When updating a remote view based on an Oracle table that contains fields of type "varchar," you may receive an Update Conflict error.
>
>But the solution of changing the varchar2 field to a memo within the VFP view is not working.
>
>To reproduce:
>1) create Oracle8 table with VARCHAR2 type columns
>2) create VFP5 remote view with necessary Update Criteria
>3) change field type of column to Memo within remote view
>4) browse, make change, go to another row.
>5) Error "Update Conflict" occurs
>
>Can use SQLEXEC pass through, but updating through remote views is not working.