>Does anyone have experience of setting up vfp remote views to SQL Server when updating on key and timestamp? It's hard to find any information on how to to set it up properly.

Yep... we use key and timestamp exclusibly for conflict resolution.

>It appears that you should not include the timestamp field in your remote view in order for it to work properly. Is this correct?

No, you should SELECT the timestamp column, only don't flag it as updateable.

>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.

Right, you get the error cause you have the column marked as updateable in your view.

>3. On the remote view 'Update Criteria' tab identify a key field and make all other fields updateable including the timestamp field.

The bold above is your mistake.

>Can anyone confirm the correct procedure?

HTH,
BOb