Mark Bakelaar
asked on
Concurrency violation on SQL delete
Hi Experts,
I compare two datatables A (Notes datasource) and B (SQL datasource) the following way:
1. Loop through all rows in A.
(A) If a row with a similar key can be found in B: update the row in B.
(B) If the row can not be found in B, create a new row B.
2. Loop through all rows in B.
(A) If no row with a similar key can be found in can be found in A: delete the row in B.
3. Update B
Datatable A and B should be exactly the same after 1 and 2.
I get a concurrency violation on the delete command "0 rows of 1 were effected" after the update command. Should I update in between 1 and 2 or use accept changes somewere to prevent this message?
Thanks in advance,
MB
I compare two datatables A (Notes datasource) and B (SQL datasource) the following way:
1. Loop through all rows in A.
(A) If a row with a similar key can be found in B: update the row in B.
(B) If the row can not be found in B, create a new row B.
2. Loop through all rows in B.
(A) If no row with a similar key can be found in can be found in A: delete the row in B.
3. Update B
Datatable A and B should be exactly the same after 1 and 2.
I get a concurrency violation on the delete command "0 rows of 1 were effected" after the update command. Should I update in between 1 and 2 or use accept changes somewere to prevent this message?
Thanks in advance,
MB
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER