**Perhaps you have some constraints defined on the SQL side that are causing this weird behavior. I dunno but it sounds like it's time to check your database schema on the server side really carefully.**

This is too bizarre. Oh well the only constraint I have is the PK constraint. Basically, it seems to me that the SQL*Server Engine wants to do a delete then insert no matter what I set the view update method to be. To get the ill-behaving views to work, I:

1.) Removed the sql TimeStamp Column from the fields list in the view (don't know what part the timestamp column plays in all this but it does have an effect)
2.) Changed the views buffering from default to optimistic table buffering in the data environment for the form.
3.) Change the view update methodology from Update to Insert/Delete
4.) Use tableupdate(.t., .t.) instead of tableupdate(.t.)

While this works, of course I am still not completely happy -- because when you don't understand something it is bound to cause more problems in the future.

I was going to try the SQL Pass-thru but I didn't get around to it -- my tables can have a lot of fields in it and I wanted to make the remote view method work

I am using the ODBC driver SQL Server 3.70.06.23 dated 11/05/98 -- is this the latest?


Thanks for everyone's suggestions

Kevin