Hey Craig,

>This is still something I'm trying to wrap my head around. You want to tell us why TableAdapters suck!?

Oh, where do I start? <g> I'm sure you've seen some of my other posts on the subject.

The main thing I don't like is that, IMHO, a DataSet should know *nothing* about where it's data comes from. Now, granted, the TableAdapter that gets generated is not part of the DataSet *class* (it is a separate class), but it *does* get generated in the same file (and thus, the same project) ... and that's not good.

We use DataSets as "transport" mechanisms. We only communicate to the server via Web Service methods which, after putting the data into DataSets, then return XML strings of that data (return MyDataSet.GetXml();). That XML string is then used to fill instantiated Typed DataSets on the client side. Obviously no DataAccess stuff is allowed client-side, so a Typed DataSet with a TableAdapter would not work in this architecture.

Plus, they only are generated for *one* table ... what happens for a DataSet that contains many tables? Won't work (at least from what I've seen ... if there *is* a way to generate a TableAdapter for all tables in the DataSet, I don't know how to do it).

I'm sure I can think of another coupla reasons if I think about it. <g>

~~Bonnie




>LOL...
>
>This is still something I'm trying to wrap my head around. You want to tell us why TableAdapters suck!?
>
>>TableAdapters suck! <g>
>>
>>~~Bonnie