Hi Bob,

I'm now including the Timestamp as an updateable field and no longer getting any errors on a SQL Server 2000 database.

I eventually isolated the problem.

I changed the default update method from 'SQL DELETE then INSERT' to 'SQL UPDATE' and was then able to include the remote timestamp column as an updateable field in the remote view, to get the correct behaviour.

I don't believe any of the manuals I read warned me of this behaviour; why am I surprised!