>You make an excellent point, but I'd like to clarify a little.

Thanks!


>
There are two things one might think about when discussing ".Net" - one is the .Net concept of having information in "the cloud" which is accessible via the Internet by many different clients. This is central to Microsoft's corporate goals. VFP plays well in this area.
>

This "concept" is not new or novel. What is novel are the tools MS has wrapped around the concept. To the extent that VFP can consume and create web services, I would agree with your assessment. But, I would not take it any further than that.

>
The other is Visual Studio .NET which is a group of developer tools (C# and VB.Net included) which are specifically designed to be useful in creating applications that provide or consume the web services necessary to the .Net initiative.
>

I don't see .Net applications limited to just consuming/creating web services. How about traditional windows applications, independent of the Web? .Net can create those too.

VFP, like VB 6, will be used for quite some time to come. There will however, be a segment of the VFP developer community that will want to make the transition to .Net. There was a time, not too long ago, when there was talk about how cool it would be if the best of VB and the best of VFP could be combined in some way. I see VS .Net as filling that need. For that reason, I see an opportunity to make contributions that will aid in the transition...

Regards,