Concurrency Problem

[Wayne Wengert]

I am running a VB.NET app on my desktop with Access 2003 as the DB. The
table I am working with has a PK made up of 2 columns. I am currently the
only user. I built my own UpdateCommand for the data adapter. The command
uses values for the PK columns in the WHERE clause ad then uses "Set" for
some (but not all) other columns. Whenever I try to do an update I get a
concurrency violation? How can that be?

Since this application is strictly a single user application, is there a way
to simply turn off all concurrency checking?

Wayne

 

[Cor Ligthert [MVP]]

Wayne,

Did you check if your dataset has changes before you update?

And if, the next question do you use autoincrement, and don't clear your
dataset and refill it after an update.

I hope this helps,

Cor

 

[Wayne Wengert]

Cor;

Thanks for the response. I do not use autoincrement (but I was planning to use it in another case - is that a problem?) Anyway, I finally found an error in UpdateCommand syntax that created an invalid value for one of the Where conditions. I fixed that and now it works.

Wayne

 

[Cor Ligthert [MVP]]

Thanks for the response. I do not use autoincrement (but I was planning to

use it in >another case - is that a problem?)

If you can avoid that, do it, use a GUID instead of that.

Cor

 

[Wayne Wengert]

Thanks - I'll remember that advice.

Wayne

If you can avoid that, do it, use a GUID instead of that.

Cor