Why did I even include the TIMESTAMP column in my remote views. I don't need it!! When I removed it --- problem solved.

>Hi Dan ---
>
>Why not leave the timestamp column blank in the new record and let SQL Server deal with a value when the server table is updated? (you have to ensure that the column is *not* updateable)
>
>
>>I have a toolbar button that users can click to append a new record and copy all values from the current record to the new one. This works fine with local tables.
>>
>>However, with SQL Server tables (remote updateable views) with a TIMESTAMP column it does not work. The TIMESTAMP value is being copied and, since it is the same as the previous record, I get error messages when I try to save the new record.
>>
>>Is there a way I can assign the TIMESTAMP value manually?