>>I am willing to go to far to avoid any involvment in any .NET pro/con discussions. >That subject is already discussed close to the saturation point. :-)
>
>aren't comments like this inviting .NET pro/con discussions:
>
>>>Well, the thing is that VFP9 is COMPLETE, there is practically nothing to add to it.
>>>VFP9 is an adult, and does not need its mother anymore.
>>>And since .NET is far from complete, Microsoft decided to transfer
>>>most of its VFP team to the .NET team.
>>>The .NET team clearly needed some bright heads! :-)
>
>>>VFP9 will fill my needs for the next 50-100 years.
>
>VFP9 is a nice little niche market product...
>Visual Studio 2005 is a better all around product in nearly every aspect....
>
>VFP is good for building LAN/WAN apps on slow old machines...
>and the WEb Connection Add on is pretty good for data centric web sites that do not require any recursive code...
>
>other than that its bye bye Foxpro
>
>
>:)

All I want to say is that for MY customer base, 5000+ users, VFP plus a few third party tools will fill all the needs for the foreseeable future, which means the next 10-20 years. And although MSFT has unplugged VFP, other companies have only just begun their work on the "next generation VFP". See http://www.etecnologia.net/ and http://guineu.foxpert.com/