Sproc was the culprit

  • Thread starter Thread starter jacob4408
  • Start date Start date
J

jacob4408

ooops! :oops: My sproc handling the delete command was of the type
"delete from table where field = parm" so the first time it was
called it deleted all the rows. Subsequent calls to the delete would
return 0 rows affected which the DataAdapter interprets as a
concurrency problem.

Whoo, glad that's over with.
 
Hi Jaboc,

Glad you answered, but please connect it to the original message, than
nobody has to take time to look that over.

Cor
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

DBConcurrencyException Not Thrown For INSERT Command 1
DataAdapter.Update returns 1 when the row has been deleted 1
Why is this one sproc so slow when using ADO.NET? 5
Using a Timestamp field to implement optimistic concurrency 2
TableMappings and FirstReturnedRecord 4
The DeleteCommand affected 0 records 2
Deleting a row from a dataset using DeleteCommand 3
DataAdapter.Update InsertCommand with multiple Tables (DataTables) 1

Back
Top