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.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
