>I've been busy and I'm just now getting around to replying to some older threads.
>
>>I understand your viewpoint on this. If I need to pass around a dataset especially with the schema info then I want it "clean" too. The TableAdapter does put a bunch of crap into the XSD. If your dataset is used for this purpose just use DataTables. You can always create another dataset to hold any TableAdapters if needed.
>
>I'm not sure what you mean by "just use DataTables" and "create another DataSet for TableAdapters".

Sorry, what I meant to say was to just use DataAdapters (or some other means) to fill your DataTables.

>
>>What? Check the provider you picked. If I select the SQL provider then SQL objects are used.
>
>I'm pretty sure that I *did* select the SQL provider when I did this before, but I just tried it again to be sure and it *does* correctly generate SQL objects, so I don't know what happened the first time.
>
>>I rarely ever instanciate a dataset from within my application. Again I do mostly web development. For winform development I would be more likely to create dataset objects and even pass them around. An example, the TableAdapter class that is generated has a GetData method that allows you to return a typed datatable. No need to create the dataset object. My dataset XSD's are used only to configure data access. It provides a visual designer where I do not have to manually code the datalayer
>
>This would not "fly" in our architecture. We only communicate to the server via Web Service methods which return XML strings, which are 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.

That demonstrates a very important point. ASP.NET is used in a variety of architectures such as Web and Winform development. Methods used to access data in a Winform application may not be appropriate for use in a Web application.

One concern I have in this forum is that it is often impossible to tell what type of application is being developed. That makes it difficult to provide a solution that "fits" the application. Maybe Michel could address this problem and provide a solution.

>
>>The TableAdapter provides access to a single defined datatable within the dataset by design. You can return multiple tables from SP to populate the dataset. To do so you have to create a new TableAdapter fill method that calls the underlying DataAdapter fill overload by DataSet instead of by DataTable (the default). If you doing this though then you just as well simply use a DataAdapter directly.
>
>Exactly my point!!!! <g>
>
>>I always value your opinion and to me it’s worth a lot. I really appreciate the time and effort given by you (as well as others) and I can never say thank you enough.
>
>You're quite welcome. I enjoy voicing my opinion. <g> I hope you (and others reading this thread) realize that I'm not trying to be argumentative, but I believe that it's good for everyone to be exposed to different architecture designs and they associated pros/cons. Doing so should enable others to make better decisions in designing their own apps.
>
>~~Bonnie