>Borislav,
>
>Thanks for the reply. I know what you are talking about with that. In this case the record has already been inserted (and the identify key field assigned) from a PHP web application when the consumer fills out an online form. The lead is collected on a website and I'm using VFP to process the lead.
>
>I still hope to figure it out but I've already resigned myself to having to do a SQL passthrough to update the backend. For now I have turned off the 'SQL Update' and I'm just using the remote view as an non-updateable cursor. That way I don't have to change any of the interface or grid stuff and will just do a SQL passthrough to perform the update. It's like doing all the updates twice (once locally to the cursor and then once by hand to the backend) but at least it's a plan. Because of the way this app functions it will not be too bad to do it this way. Just irks me a bit that it's when the data doesn't change that it throws the error but when the data does change it does not error. Too weird.
>
>Greg

Greg,
what happens if you build a small application that uses a CursorAdapter and use ADO instead of ODBC? Maybe there is some bug in MySQL ODBC driver?
Is there any tool in MySQL to check what queries VFP sends back to MySQL (something like SQL Profiler), just to see what is happening when you send no changed values to Backend?