S
steve
Datasets are great because you can manipulate the table data they
contain in a disconnected state, right? Then simply call the Update
method on the adapter that created the contained table to write
changes back. But the controls I use to effect these data
manipulations launch repeated postbacks. I'm saving the dataset in
ViewState and reloading on PostBack, but the original DataAdapter is
long gone by the time I'm ready to write the multiple changes back.
What am I missing here? Sure, I can get around this by immediately
writing each change back to the db and refilling the dataset on
postback, but that kind of kills the spirit of the disconnected
dataset.
contain in a disconnected state, right? Then simply call the Update
method on the adapter that created the contained table to write
changes back. But the controls I use to effect these data
manipulations launch repeated postbacks. I'm saving the dataset in
ViewState and reloading on PostBack, but the original DataAdapter is
long gone by the time I'm ready to write the multiple changes back.
What am I missing here? Sure, I can get around this by immediately
writing each change back to the db and refilling the dataset on
postback, but that kind of kills the spirit of the disconnected
dataset.