Hi.

Is that a good practice for every table to have its own DataAdapter and
DataSet?

Emil.

"EmilH" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...

> Is that a good practice for every table to have its own DataAdapter and
> DataSet?

IMO, no. For one thing, every time you create a new table, or modify an
existing one, you'll need to change your app...

Use a decent DAL (database abstraction layer) based on the Microsoft DAAB
and you'll be fine...
http://dotnetjunkies.com/Article/29E...7F100A9F9.dcik

--
http://www.markrae.net