JimB,
>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.
Exactly!
Best,
DD
A man is no fool who gives up that which he cannot keep for that which he cannot lose.
Everything I don't understand must be easy!
The difficulty of any task is measured by the capacity of the agent performing the work.
