Updates in a transaction

  • Thread starter Thread starter Guest
  • Start date Start date
Dick,

You maked it clearer, however
However, my real issue is that the original dataset, the one we'll go back
to if we have some problems, won't include the error messages applied
during
RowUpdating and RowUpdated - because these error messages have been
applied
to the copied dataset, the one we passed to the dataadapter.
Click to expand...
From this I suggested that you made by instance from your dataset a clone.
Than you can add to that clone the rows which are wrong. (You can even add
an extra column to set the errors).

The primary keys stays the same, and therefore you should in my opinion be
able to do with that your error handling going in the way you are now busy.

However, for that are more ways to go.

Did you get that message as well?

Cor
 
Thanks for your help in on this Cor. I think the conclusion is that, until
the next version of .net at least, I can't easily achieve what I'm trying to
do. I realise I can code my own mechanism for getting error messages back
into the original dataset and therefore back to the UI but I think the effort
outweighs the benefit. For the time being I'm going to take out the
transaction. This means that each update will live or die independantly. But
that is OK because the dataset keeps track of this and therefore the user
will be well informed.

Again thanks for you help.
 
Dick,

Sorry I've been incredibly busy and haven't had a chance to be as regular in
NGs as I'd like to be.

But to answer your question, in this scenario, you will have to hand merge
the dataset back. That is actually easier than it sounds, just pick up a
copy of reflector (free), and almost copy paste the code in your own
application.

- Sahil Malik [MVP]
http://codebetter.com/blogs/sahil.malik/
 
Back
Top