By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
448,773 Members | 1,793 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 448,773 IT Pros & Developers. It's quick & easy.

Concurrency violation errors

P: n/a
Hi

During db development one of the most frustrating thing is the Concurrency
Violation error which seems to be a general error message for any error
during saving of record(s). How can one debug such an error and get more
specific information on the underlying reason for error and the
fields/records responsible for it?

Thanks

Regards
Feb 12 '08 #1
Share this Question
Share on Google+
2 Replies


P: n/a
John,

As you have done it well, then there should be seldom a concurrency error.
It is even mostly difficult to test (get them) because you should use two
operations seperately from each other to get those.

Therefore you should at least first tell how you created your checking on
concurrency. Because there are more ways to prevent concurrency problems
(not the errors because concurrency checking has to be done as it is at
least a little bit a business solution).

Any other answer you get now, will be a waste of time for the writter and
for you to look at it. Then you can better set your money on one of the
races in the UK.

However it is for sure not a general message. Normally as you have done it
well, you would see them very seldom as optimistic concurrency is based on
that.
Cor

Feb 12 '08 #2

P: n/a
How are you doing your updates? Are you using strongly typed datasets and
the auto-generated SQL statements that do the updates? Or are you rolling
your own?

RobinS.
-------------------------------
"John" <Jo**@nospam.infovis.co.ukwrote in message
news:ee**************@TK2MSFTNGP03.phx.gbl...
Hi

During db development one of the most frustrating thing is the Concurrency
Violation error which seems to be a general error message for any error
during saving of record(s). How can one debug such an error and get more
specific information on the underlying reason for error and the
fields/records responsible for it?

Thanks

Regards
Feb 13 '08 #3

This discussion thread is closed

Replies have been disabled for this discussion.