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.