I see. The way I create typed data set is by using a method from KG book where - in a project used only during design phase - a typed data set is created and then saved to an XML file. Then this XML file is added as an existing item to the project. Since the process of creating the XML file is automated, recreating the typed data set in my data set project is easy.

As to your comment "unnecessary" stuff. Why did MS not improve their design when moving from .NET 1.1 to 2.0? I would hope that they keep improving their product. It is a rhetorical question.

>It's not so much changes to the designer-generated class that I object to, it's that the .xsd *itself* gets changed to include a lot of unnecessary (IMHO) stuff. That's what sucks.
>
>~~Bonnie
>
>
>>>>UPDATE: I have learned that I can just open the data set in designer and change the type of the column to Boolean. So this should do the job.
>>>
>>>That'll work as long as you open the DataSet with the XML view, not the designer view (with the little boxes that represent the tables). If you open in the designer view, make a change, then save, a whole bunch of extra junk gets put in your .xsd ... really clutters it up. If it's already cluttered up with that extra junk, then I guess it doesn't matter. But, I prefer clean, un-cluttered .xsd's, so I always make changes to the XML itself.
>>>
>>
>>I actually used the designer when changing the type. I have not looked inside the DataSet class to see what type of "clutter" is added in this case (not that I would recognize it). So what I will do is delete this typed data set class and recreated it again from an XSD file.
>>
>>Thank you for your suggestion.