>the Designer creates an .xsd rather than using a utility. In our utility, it's simply a matter of getting a DataSet by calling a Stored Proc (you would execute SELECT commands) and then creating an .xsd by using the DataSet.WriteXmlSchema() method.

Hmm... I think what I'm not getting is what the .XSD is used for. I had assumed it was used by the IDE for creating the DataSet.Designer.cs file, are you using the .XSD at run time in your programs?

>Yes, and here's part of my point ... the connection string shouldn't even be *in* the DataSet class. A connection string should have absolutely *nothing* to do with a DataSet. The connection string belongs in the DataAccess layer and, IMHO, this is separate from the DataSets.

That part I got and it makes perfect sense to me.

I appreciate your help on this, there is so much to understand when you are getting ready to write decent sized apps in a new language. Understanding the basics of how to lay things out in the new system really helps!