Hi Jess,

Well, first of all thank you for your kind words.

Now.. As to whether or not VFP should be a .NET-based/enabled product: I do not think it should so be. Most of the reasons have been discussed extensively here and elsewhere. The 'bottom line' that I have seen is that for VFP to participate in the CLR it would give up so much of what FoxPro offers as to end up making FoxPro not be FoxPro.

So.. If you think about this a little here are the alternatives:

1) Change VFP into something that would make it so similar to existing products as to effectively and thoroughly destroy it.

2) Leave it out of the CLR and therefore keep those features that differentiate FoxPro from the other products and perhaps allow Visual FoxPro to extend itself into the future.

IOW, it seems to me that your concerns about FoxPro's demise by not being a part of .NET are incomplete in that if FoxPro were to become a part of .NET it would no longer be needed. VB.NET could handilty take its place and the demise of FoxPro would only be more certain.

My advice: Keep Visual FoxPro out of the CLR.





>Doug,
>
>Before opening your response to me, I already answered Mike's comment. I really admire your principles. Your replies makes one's perspective in a balancing act.
>
>On a final note and this is not intended for anyone: "Technical expertise will go garbage without the sense of decency..."
>
>>Jess,
>>
>>>Doug,
>>>
>>>>Well, I'm something of an optimist. <g>
>>>
>>>IYO, which is better one, optimist or realist?
>>
>>Must one presume that being one means not being the other?
>>
>>A false choice I'd think Jess...
>>
>>Candidly, I think the more realistic one is, and the more one accepts reality, the happier and more optimistic one will become.
>>
>>I will die some day. Death holds no fear for me. My sins have been forgiven. I will live forever in the light of God's love. I have dealt with the reality of this life and the one to come.
>>
>>I'm very optimistic. <g>