LOL!! I'm sure that we've disagreed on this one before, Rick. But that's ok.

Slow to load? I don't think so. I just did some benchmarks on a 27 table typed DataSet. We have larger ones in our app, but this just happens to be the one I was currently on.

Instantiating that DataSet (the first time it's used) took .06 seconds. Wow! That'll really bring my app to it's knees. After it's been instantiated once, it takes 0 seconds to instantiate subsequently ... yeah, I suppose that's because it's caching it all in memory, but so what ... I don't necessarily see that as a bad thing, maybe you do.

Won't work if you return anything other than what they're designed for? Well, that all depends on what you mean by "won't work" ... the DataSets will work just fine. It's just that you won't have the strong typing for any additional columns or tables that you may have returned and you'll have to use the regular DataSet syntax for accessing those extra columns or extra tables. No big deal.

Sorry, Rick. The benefits of using a Typed DataSet far outweigh the measly excuses you've just made. Got anymore? <g>

~~Bonnie





>>I was an early promoter of typed datasets. I don't know why anyone would want to use anything else!! <g>
>
>Because they are slow to load? Because they load all schema before every use? Because they won't work if you return anything but the exact data that was pre-generated (ie. they won't work with dynamic query results).
>
>Need more? <g>
>
>Awful things those typed datasets.
>
>+++ Rick ---