DataSet vs. DataTable

[slvrscremr]

Here's the query... I have an object that implements ICollection and want to expose it via a webservice. From everything I've read, the easiest approach is to dump the relevant data into an XML friendly object (i.e. DataSet, DataTable) and return (voila!). The question being more about style than substance, since I am not ever going to be returning more than a single datatable from a collection object, should I simply transform the data into a DataTable than a DataSet? The main benefits I've experienced from using DataSets come from managing multiple DataTables and their relating data... neither of which apply here. Am I on target or missing something? :cool: Darien "I don't know. I haven't tried today." - Trumpet icon Maynard Ferguson's response when asked how high he could play.

[Tad McClellan]

I don't think datatables are serializable (for reasons only known to microsoft developers) so use a dataset. I think this is also fixed in vs 2005.

[minhpc_bk]

Hi there, Just second the previous post, you will have this problem when you use a datatable as the return value of a web service: Problems using an XML Web service that returns a DataTable[^]

[slvrscremr]

Thanks. I would have never guessed in a million years. Darien "I don't know. I haven't tried today." - Trumpet icon Maynard Ferguson's response when asked how high he could play.

[slvrscremr]

Thanks for the reference. Darien "I don't know. I haven't tried today." - Trumpet icon Maynard Ferguson's response when asked how high he could play.