Still, the typed dataset only solves one shortcoming, casting. It still an in-memory database, a relational thing. It doesn't replace an object model. Typed datasets are not object-oriented.

>Dave,
>
>One should note that the article is talking about un-typed DataSets, not Typed DataSets. To quote from the article:
>
>Finally, note that when I refer to DataSets, I don't mean typed-DataSets, which indeed solve some of the shortcomings associated with untyped-DataSets.
>
>An important distinction, IMHO.
>
>~~Bonnie
>
>
>
>>This is a great article on MSDN on why not to use the DataSet as the basis for your business objects.
>>http://msdn.microsoft.com/asp.net/default.aspx?pull=/library/en-us/dnaspp/html/custentcls.asp