Thanks Bonnie,

Generating the xsd wouldn't be a problem if all I had was a single dataset but as I mentioned every business object uses its own. Even with the single table I have a problem with the fact that the typed DataSet when it pulls the first data generates all the tables.

>Hey Rick,
>
>>>Can you elaborate a little on this process. I just thought this over and come to think of it getting the XSD generated wouldn't be too difficult. One could just set up a little utility form where you load all tables into a DataSet and let it generate the schema for you I suppose.<
>
>Right, that part isn't difficult at all, and that's basically what gets done.
>
>>>Then what though? I mean we need the generated .cs fiel from the xsd and the generation doesn't happen automatically does it?<
>
>No, it's not automatic. Once you have gotten the .xsd (either a new one, or a modified one), you then have to do the Generate DataSet thing in the UI (there may be a way to automate that, but I have no idea how ... it's easy enough to right-click the .xsd in the Designer, and then toggle the Generate DataSet).
>
>Now, here's where we cheat (and Glenn's idea comes into play) <g> ... we have a little VFP .prg we wrote to tweak stuff and spit out some more code. All you have to do is copy the generated .cs to the clipboard and run the VFP utility and it puts more code back in the clipboard that you paste into a new class. This new class is a subclass of the generated Typed DataSet and is the class that we use for our Typed DataSets. I hope that doesn't sound too confusing. I can probably give you the VFP code (if you're nice to me <g>) ... god knows I've used enough of your code from Foxpro Advisor back in the early days. <g>
>
>~~Bonnie