>Jess,
>
>>How about making CLR optional in VFP.Net thus making it backward compatible?
>
>It is my understanding from the developers of VFP that that is not an option. Either VFP gets stripepd down to be a .NET language or it doesn't.
>
>I don't understand what the big issue is. If you want to build .NET classes then use VB.net or C# or C or any other .NET language, build the class you want and then use it from VFP.

Maybe some just would like to leverage what they have rather than begin a cycle of developing expertise all over again.

VB has VB, VBA and VB Script and now, I guess, VB.NET. The concept of having similar for VFP is difficult to see?????

You may already be a pro in VB.NET and/or C# as well as VFP, but for most of us it has taken us years to get to where we feel we know and understand the nuances of VFP. It seems reasonable to assume that other languages have their nuances too. The ones I have used in my career sure have had!

I know that it would take a very long while before I called myself highly skilled at, say VB (.NET or otherwise). After all, all of my work involves DATA. So not only would there be nuances of VB, but also of ADO and xxx and yyy.