Angie,

When you do your first TableUpdatE() the timestamp on the server is updated. The timestamp column in your remote view is not automatically udpated. If you attempt another TableUpdate() without a requery(), your remote view's timestamp is different than that on the server, generating the error. The solution is to requery() (or use some other method to update the timestamp column) after the tableudpatE().

>Hello everyone,
>
>I am having an issue with the above. I have a view that includes a timestamp column. I have the WHERE clause set to Key & Timestamp. The timestamp column is part of the SELECT field list. The timestamp column is however marked as non-updateable.
>
>The problem is as follows. If I make a change to the view and save the changes, all is well and the update succeeds. If I then make another change to the view and attempt to save it, I get the above error message. The error recommends to revert the table or update with "Force" mode. If I revert the table and try to re-save it, I still get the above error message.
>
>I have not tried to update the table with "Force" mode because there have been no changes made by any one else and besides, I obviously need to detect real update conflicts :)
>
>Whilst it may appear that another user might have made changes, this is most definately not the case as I have only just developed the table on SQL server, it is on a development server only and there is only me working on the table.
>
>If I change the SQL WHERE clause in the view to Key & Modified fields, everything works as expected?
>
>Any insight to this would be great!
>
>Regards,
>
>Angie.