B
bill
Hi all,
I 've just start moving from ADO to ADO.NET and have a
question regarding optimistic concurrency. As
in "Optimistic Concurrency Example" from "NET Framework
Developer's Guide" when an update conflict occurs such as
when the user try to update a row that has already been
updated or deleted by another user. In case of such
conflict the "DBConcurrencyException" that were thrown
when I call DataAdapter's update method only give the
message indicating that the "violation occurs" and "0
records were affected", the "RowError" method of
the "Rows" collection also give a similar answer. My
question is how can I know the exact reason of the update
conflict, whether the row was already deleted or had
already been updated. Is there a method in ADO.NET classes
that give the exact reason of the conflict or do I need to
use some other technique to find out. If possible you
could give some example code or point me to the rigth
location. Thanks you for your time.
Regards,
I 've just start moving from ADO to ADO.NET and have a
question regarding optimistic concurrency. As
in "Optimistic Concurrency Example" from "NET Framework
Developer's Guide" when an update conflict occurs such as
when the user try to update a row that has already been
updated or deleted by another user. In case of such
conflict the "DBConcurrencyException" that were thrown
when I call DataAdapter's update method only give the
message indicating that the "violation occurs" and "0
records were affected", the "RowError" method of
the "Rows" collection also give a similar answer. My
question is how can I know the exact reason of the update
conflict, whether the row was already deleted or had
already been updated. Is there a method in ADO.NET classes
that give the exact reason of the conflict or do I need to
use some other technique to find out. If possible you
could give some example code or point me to the rigth
location. Thanks you for your time.
Regards,