I'm going to put typed data sets on the "must look at list", but will continue my project the way I'm going now. In the next month or so, I'll be working on existing code so I'll have to do things that way...but what way it is, I have no idea right now.

>That's a long-standing argument. ;)
>
>Seems that half love them, half hate them. I use them. IMO, you can develop 10 different types of apps with typed datasets, and yield different productivity gains.
>
>The power of the new List class in VS2005 makes custom collections a 'better choice' than in VS2003.
>
>Someone raised a point that sometimes a language is chosen for you (e.g. you come into a project where the language has already been chosen). Same applies here....some projects are going to use typed DataSets, some will use custom collections (and some use both!). My two cents is to use them, but also familiarize yourself with custom collections.
>
>Kevin