Hi Folks

I am using the DDT to create my DML sprocs.

All of my tables have an integer identity field as the PK and a TimeStamp column named RowVersion for use with concurrency.  When I generate the sprocs using the DDT, I get this error on all of the Update and Insert statements (the deletes work fine)

Cannot insert an explicit value into a timestamp column. use INSERT with a column list to exclude the timestampe column, or insert a DEFAULT.

I tried setting the default to 0 in the DDT table structure interface but get a broken rule.

I understand why I'm getting this error but not sure what to do about it. When using  TimeStamps, do I need to do this piece manually?

Thanks!

Clay

Thanks Larry

Unfortunately, the problem is in generating the stored procedures themselves and not in the business objects.

I'm thinking that this is a bug in the stored procedure generator. It sounds to me like the generator is trying to Insert into and Update the TimeStamp column.

Clay

In the table properties, where you check the boxes to generate the stored procedues, did you set the concurrency type on Update (and maybe delete if you want) to Optimistic Timestamp?  And you also have to specify the field in the combo box at the bottom to tell what field is the row version column (so that it gets left out off the inserts and updates).