On a similar note, there is a free .Net code generator called Code Smith. It uses templates to create the code. The templates are asp.net like. Just regening all your typed data sets after any data change may be the simple answer.

I just ran it, it comes with a csharp typed data set code generator.

http://www.ericjsmith.net/codesmith/overview.aspx

BOb


>Glen,
>
>The Key to .Net dataaccess is wrappers <g>. I and many others have build business classes that make data access pretty painless. In fact you may recognize wwBusiness (from Web Connection) in some of the new stuff I'm doing (Web Store .Net for example) which works very similar to the way I had it working in VFP.
>
>Somethings are also easier. For example generating the Xsd is pretty easy - just load the data then output the schema. THat support is actually built into the dataset, so in a lot of ways this is easier than it is in VFP say. Outputing a complex schema and getting all the type data correct manually is not an afternoon project either <g>... been there done that with wwXML a long while back.
>
>
>But I have actually used VFP on a few occasions to generate code for VS.Net, it was definitely a bit quicker and easier, but then again that was a while ago when I was still struggling with a lot of things in .Net. All better now, but as you see there are a still a lot of things to learn...
>
>
>+++ Rick --
>
>
>
>>Sorry, I cannot help you Rick with this problem as I have not yet experienced it. I am just stqrting with .NET and got a great "Hello World" program is you need it <bg>.
>>
>>But as I was floundering thru the reams of code required to access and modify data it occured to me that VFP may be the answer. We can code a code generator in VFP which will spit out the .NET source code we need. VFP being Data Centric, understands data very well indeed, and can be used to create tools for .NET were .NET is very required laborious coding. Perhaps a generator to create the casting code you need for your tables would be a good start.
>>
>>Glenn
>>
>>
>>>Hi all,
>>>
>>>I've been sitting on a fence here trying to figure whether I should use typed datasets or stick with untyped datasets. So far I've been using untyped datasets simply because I don't have to worry about keeping database and schemas in sync. And I'm getting real tired of having to explictly cast everything coming out of a DataRow <g>...
>>>
>>>What are other people doing?
>>>
>>>While I see the benefits in using typed datasets I just can't see how how to efficiently automate the process of keeping the XSD schemas and generated DataSets intact when data changes occur. Due to how my business objects work I would have a lot of separate XSD files (one for each business object and it's main table view).
>>>
>>>I also worry about app bloat and performance here. There's a lot of code that gets generated for typed datasets - a lot of it that gets loaded uselessly (for example all datatablews are created up front even if you never fill the table)... Typed Datasets are faster with accessing the data in a loop but otherwise there's a perf hit.
>>>
>>>I'd love to hear how you are using typed datasets if you are using them...
>>>
>>>+++ Rick ---