I have a web form where I’m updating several biz objects. If I issue SaveDataSet on one and then the next one fails due to rule violations the first one is rolled back as it should.

Problem: If the first Biz object was an ADD, after the rules are corrected in the second biz object and the SaveDataSets are called again, the first biz object data is not inserted into the database. It seems that once the dataset has been Added within the transaction and then rolled back it can’t be Added on subsequent calls to SaveDataSet I’m using the simple command builder method to do the updates.

I’m thinking this may be a problem with ADO.Net and the command builder within transactions. After the first insert on the first dataset the newly added row’s rowstatus is changed from ‘Added’ to ‘Modified’. This leads me to believe that on a subsequent calls to update, ADO attempts to do an update instead of an insert, in which case the row would not be added.

Has anyone encountered this problem? Is it an issue with ADO.Net or should I continue to look in the MM framework for the answer?

I intend to eventually do updates with stored procedures but I like the ease of prototyping an application just using basic command builder updates.

Thanks in advance.

Terry Carroll