It appears that you should not include the timestamp field in your remote view in order for it to work properly. Is this correct?
Other aricles I have read say indicate that you must include the timestamp field but when I do this the Tableupdate fails with error 1585 'update conflict' and I lose the top record in the view.

I don't have a definitive answer and when I go to look at my remote views some have the timestamp column included and some don't. The ones that don't were probably removed because of problems. My suggestion is to include the timestamp field in the sql*server schema, but DON'T include the timestamp field in the remote view. I don't have any hard facts to back up my opinion, but it seems to work best this way.

Kevin