DataSet updates

[Random]

What I want to do is to carry a DataSet through a multi-page process. Each
page will have an interface for updating and/or inserting records in
individual DataTables. At the end of the process, I will submit the entire
DataSet (through DataAdapters) back to the database.

Filling the DataSet schema seems simple enough. Binding controls to the
DataTables/DataViews is fine as well. But I am coming up woefully short on
resources to instruct me on how to update the in-memory DataSet when edits
are made, and how the DataSet processes multiple records on the database
when it's Update method is called.

[Axel Dahmen]

You sure already know that HTTP is a stateless protocol. So I guess you're
saving your DataSet into a Session variable.

You can bind your asp:Repeater, asp:DataGrid etc. controls in the Page_Load
event:

MyDataGrid.DataSource = Session["MyDataSet"];
MyDataGrid.DataMember = "MyDataTableName";
MyDataGrid.DataBind();

HTH,
Axel Dahmen

--
www.sportbootcharter.com

-------------------------
"Random" <ci*******@hotmail.com> schrieb im Newsbeitrag
news:ee**************@TK2MSFTNGP10.phx.gbl...

What I want to do is to carry a DataSet through a multi-page process. Each page will have an interface for updating and/or inserting records in
individual DataTables. At the end of the process, I will submit the entire DataSet (through DataAdapters) back to the database.

Filling the DataSet schema seems simple enough. Binding controls to the
DataTables/DataViews is fine as well. But I am coming up woefully short on resources to instruct me on how to update the in-memory DataSet when edits
are made, and how the DataSet processes multiple records on the database
when it's Update method is called.

[Joe Fallon]

David Sceppa's book on ADO.Net is a fantastic resource.
It explains all of this in great detail.
--
Joe Fallon

"Random" <ci*******@hotmail.com> wrote in message
news:ee**************@TK2MSFTNGP10.phx.gbl...

What I want to do is to carry a DataSet through a multi-page process.
Each page will have an interface for updating and/or inserting records in
individual DataTables. At the end of the process, I will submit the
entire DataSet (through DataAdapters) back to the database.

Filling the DataSet schema seems simple enough. Binding controls to the
DataTables/DataViews is fine as well. But I am coming up woefully short
on resources to instruct me on how to update the in-memory DataSet when
edits are made, and how the DataSet processes multiple records on the
database when it's Update method is called.

[Random]

Thanks for the referral. I'll check it out.
"Joe Fallon" <jf******@nospamtwcny.rr.com> wrote in message
news:up*************@TK2MSFTNGP11.phx.gbl...

David Sceppa's book on ADO.Net is a fantastic resource.
It explains all of this in great detail.
--
Joe Fallon

"Random" <ci*******@hotmail.com> wrote in message
news:ee**************@TK2MSFTNGP10.phx.gbl...

What I want to do is to carry a DataSet through a multi-page process.
Each page will have an interface for updating and/or inserting records in
individual DataTables. At the end of the process, I will submit the
entire DataSet (through DataAdapters) back to the database.

Filling the DataSet schema seems simple enough. Binding controls to the
DataTables/DataViews is fine as well. But I am coming up woefully short
on resources to instruct me on how to update the in-memory DataSet when
edits are made, and how the DataSet processes multiple records on the
database when it's Update method is called.