G
Guest
I keep getting a concurrency exception the second time I make a change and
attempt to update a dataadapter. It appears this is by design, so there must
be something I can do to avoid it.
Example:
I have a dataadapter that contains one table with one row. I change the
value of the 'FisrtName' column in that row from Jack to John. I call
..update on the dataadapter it goes through fine. Now I change that same
column in that same row from John to Peter. Update fails. I'ts because the
'origianl' value is still getting passed as the parameter value in the update
command. In other words, it is looking for a row where firstname = 'Jack'
and finds none.
How do you get the updated values to become the current values for
subsequent updates without making an additional run back to the database to
refresh the whole dataset?
Thanks!
attempt to update a dataadapter. It appears this is by design, so there must
be something I can do to avoid it.
Example:
I have a dataadapter that contains one table with one row. I change the
value of the 'FisrtName' column in that row from Jack to John. I call
..update on the dataadapter it goes through fine. Now I change that same
column in that same row from John to Peter. Update fails. I'ts because the
'origianl' value is still getting passed as the parameter value in the update
command. In other words, it is looking for a row where firstname = 'Jack'
and finds none.
How do you get the updated values to become the current values for
subsequent updates without making an additional run back to the database to
refresh the whole dataset?
Thanks!