cant see cause for concurrency violation

F

fguihen

Well-known member
Joined
Nov 10, 2003
Messages
248
Location
Eire
i have a tabcontrol , and each tab gathers some info the user thats regestering. when the user gets to the last tab page the collected data is passed to an object that sends the data to the database. everything is saved, but if i then go back and change some data one one of the tabs and try to update it i get a concurrency violation. i have update commands set up on all my data adapters so i dont see why the data that i saved cannot be updated when i submit the record again with slight changes. any ideas?im using c# and ms access database so there are no other users.its driving me nuts
 
The Problem might occure with Autoinc ( Identity ) Fields.
The Commandbuilder doesnt generate code to get these after the update,
so they might be different.

If there is not that much data, clear the DataTable and read it in again,
than you are save.
 
its not. i generate the identity field in my form so the database has nothing to do with that. i can add and delete fine, its only when i try to update. stupid concurrency violation. thanks anyway
 
Back
Top