I think the concurrency violation means that the records are currently being updated already or that they have an exclusive lock on them. One time I found that while connecting to an Access database on a Win2000 local machine; that this error was given falsely. After I compacted and repaired the database in access, the error was gone. I kind of think that .NET is a little buggy, but check to make sure another command isn't updating the same records.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.