>>No.. just one where SQL DELETE/INSERT was used for all updates. Why would you modify a key field?
>
>An example would be a "salesrep" table where one of the keys is the "salesarea". Key is "modified" when the salesrep is assigned to a new salesarea.

Ah... then SALESAREA is a FORIGEN key... you don't identify that as a key in the view... when you define the view you only specify the fields that create the PRIMARY key of the table. So, for a salesrep table your pirmary key would be something like RepID.

So, if you changed the salesarea FK you would send an update like...

UPDATE salesrep SET salesarea = 'ny5' WHERE RepID = 'A57YT'

So... you replace the FK sales area in the record identified with the primary key of RepID A57YT.

So, if you set up a Remote View of the sales rep table, only the RepID would be marked as a key field.

>>Hmm.. I would talk to the ODBC author and see if they are aware of this problem. Are you using VFP 6.0?
>
>Yes it is VFP6 with Service Pack 2. Do you imply that the "bug" may be one in MyODBC( the ODBC driver for MySQL)?

Yes... since this behavior doesn't happen when I use MS-SQL ODBC driver.

BOb