>DataSets, IMHO, should know nothing about where its data comes from ... likewise the DataSet should know nothing about how to save itself to the database.
>
>DataAccess class of course ... is that what you meant? DataSets, IMHO, should know nothing about where its data comes from ... likewise the DataSet should know nothing about how to save itself to the database.
>
>OK... I guess I was envisaging something stateless (like a Web Service) in which the middle tier would create and send out the DataSet and then forget all about it until its return. In that scenario I guess you'd recreate the DataAccess class on receipt of a returning DataSet and work from there. Got it, thanks.

Right. We pass an XML string representation of the data (MyDataSet.GetXml()) back-and-forth through Web Service methods, so yeah, everything's recreated server-side with every call to the backend.

~~Bonnie