Yes, the strongly-typed data set (as well as data sets in general) are the source of much debate. Even the guru opinions are all over the spectrum...

Markus



>>>" Being strongly types is also what's make .NET more difficult to work with databases."
>>>
>>>Emmanuel,
>>>
>>>Can you elaborate on that? I don't understand the connection.
>>>
>>>Kevin
>>
>>I believe he actually has a point, although I do not think it is more difficult, rather the opposite. However, I believe he may be talking about the .NET learning curve for VFP developers.
>>
>
>Keep in mind that I'm new to .NET. I'm exploring it but not using it yet for production development. In fact, I was refering to the strongly typed dataset. It needs a wrapper (auto-generated by Visual Studio) that takes a gazillion lines of code. Without this strong-typed dataset, you have to type a lot of more code.
>
>>Strong typing is probably the single biggest diffrence between VFP and .NET.
>
>Yes, and when we get used to it, the code feels so much more robust.
>
>I don't if it's the single biggest difference. I have a feeling that it takes more time in .NET to do the same things. It's maybe due to my inexperience with the framework, but there are a lot of things about which I'm thinking "there must be a better way to do this". In a single word, .NET feels less RAD then VFP.
>
>>It requires a paradigm shift, while many other things in .NET are just more of the same (as in "I need to learn what the name of the method is that does X, but I already know what methods and objects are...").
>>
>
>I also think that .NET force us to better programming practices while VFP let you do any kind of spaghetti code without ever complaining.
>
>>You can find some information on the impact of strong typing at the following URL:
>>http://www.eps-cs.com/VFPConversion/VFPvsNET.aspx
>>
>>Check out the "Comparing OOP..." paper.
>>
>>Markus