IMO, the data adapter is a marginally useful entity. When you get down to it, the data adapter is nothing more than a way of collecting and coordinating command objects. The fill and update methods are black box wrappers that broker access to the respective commands. IMO, you are better served by creating your own data adapter and handling the tasks of filling data sets and updating data with your own custom methods.



>>We have DataSets that contain many tables (a parent and many children).
>
>I had heard to specifically stay away from that model and limit datasets to one table - I believe primarily because of diffculty with data adapter or perhaps the command builder?