>Using TableAdapters or not is something I'm still figuring out. I was hoping Bonnie would jump in here.

Sorry Craig ... it figures that just about the time this thread started was when I was heads-down in a crunch at work and I barely had time to come up for air, never mind having time for the UT. <g> Hopefully I will have some time to read this whole thread (but it's *very* long)!

You saw at least part of the other thread in the .NET forum ("Can't delete row" I think it was called) where I listed some of the things I didn't like about TableAdapters.

Basically, TableAdapters are kind of like wrappers for DataAdapters. They don't give you any additional functionality ... the main benefit might be some automatic code generation, but that benefit all goes out the window if your DataSets have multiple tables. A TableAdapter would only be generated for the first DataTable in your DataSet only.

Creating a TableAdapter puts extra code in the DataSet's .xsd file. This ties that .xsd specifically to it's source of data. IMHO, the .xsd should be nothing more than a schema representation of the DataSet. It should never know anything about it's source of data.

These two items alone turned me off totally to TableAdapters. So ... there you have it. =0)

~~Bonnie




>Using TableAdapters or not is something I'm still figuring out. I was hoping Bonnie would jump in here.
>
>>PMFJI, but I have used TableAdapters before and they are easy to use, but I have heard that they do not fit into a proper architecture.