|
-
June 23rd, 2009, 01:52 PM
#3
Re: OleDB Concurrency Violation in MS access
 Originally Posted by RaleTheBlade
. Its a pretty generic error sometimes and can boggle the mind..
 You are such of right. It confuses a lot, especilly becaue it only occurs when I add the data and without restarting the application trying to change some of the just added data. Like for example a person does an entry and when it was done and stored he detects that he has done an error and corrects the data. Just a simple situation which always could happpen.
Originally Posted by RaleTheBlade
. ...I would check to make sure the data that your sending back to the database has the same column count as what the table in the database is expecting.
Yea, there are no null fields and as I'm working with the DataTable, DataAdapter always all columns are used to be updated.
I really dont get it into my mind.
 Jonny Poet
To be Alive is depending on the willingsness to help others and also to permit others to help you. So lets be alive. !
Using Code Tags makes the difference: Code is easier to read, so its easier to help. Do it like this: [CODE] Put Your Code here [/code]
If anyone felt he has got help, show it in rating the post.
Also dont forget to set a post which is fully answered to 'resolved'. For more details look to FAQ's about Forum Usage. BTW I'm using Framework 3.5 and you ?
My latest articles :
Creating a Dockable Panel-Controlmanager Using C#, Part 1 | Part 2 | Part 3 | Part 4 | Part 5 | Part 6 | Part 7
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote
