E EmilH May 10, 2007 #1 Hi. Is that a good practice for every table to have its own DataAdapter and DataSet? Emil.
M Mark Rae May 10, 2007 #2 Is that a good practice for every table to have its own DataAdapter and DataSet? Click to expand... 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/29EF3A4F-A0C2-4BB2-A215-8F87F100A9F9.dcik
Is that a good practice for every table to have its own DataAdapter and DataSet? Click to expand... 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/29EF3A4F-A0C2-4BB2-A215-8F87F100A9F9.dcik
