Hi Charles,

Don't know if you got this figured out yet or not ... I've been away from the UT since last week and just saw this thread now. You can write a quickie little utility for creating your .xsd schema. I have the basic code needed in a blog post I wrote:

http://geek-goddess-bonnie.blogspot.com/2010/04/create-xsd.html

All you'd need to add is an easy way to execute that code (create a littly utility form or something). I have done that already, which is what I use when I need to generate an .xsd from a Stored Proc ... but I only posted the essential code in my blog.

Hope it helps ...

~~Bonnie




>>HI, Charles, I have some code that is a bit outdated (in the sense that it doesn't rely on the entity framework....just good old fashioned .NET generics and typed datasets).....but here's what it does:
>>
>>1) Suppose I have a typed dataset (call it dsOrders), with relations built in
>>
>>2) Suppose I have a stored procedure that I call (either with parameters or without) that retrieves multiple result sets
>>
>>3) I want to populate the typed dataset based on the results of the stored proc. So basically...
>>
>>MyDataClass.PopulateTypedDataSetFromProc( InstancedofTypedDataSet, "procedureName");
>>
>>
>>
>>I have a .NET class that does this. Again, a tad outdated, but maybe would still work for you. Let me know if that's what you're looking for.
>
>Thanks, Kevin. (I copied you on my reply to Tracy as well ). My problem is simply #1 above. How can I create the schema for that dataset from the sproc itself so i can see it at design time. If I use Add Datasource and point it at a sproc I get the structure of the first table it returns, but it ignores the rest. I like the convenience of having it read from the sproc but I also want to use a single sproc for each report, which will often require multiple tables.