now he got you suckered into another pointless debate after all?!

>>>I won't be suckered into another pointless debate with you.
>>
>>Be that as it may, to say that support of the product to 2010 somehow translates into something meaningful that people can hang their hat on is absurd.
>
>A vendor dropping "support" for a tool doesn't by any stretch of the imagination means that the tool itself instantly breaks. Every product has a finite support lifetime, Microsoft does a fairly good job of stating these dates on it's website.
>
>John - It is an absolute fact that people are still out there supporting FP1.x, FP2.x, VFP3, VFP5, VFP6, VFP7 apps. Heck I think it's even a safe bet that some people are out there still supporting some MSBasic, VB4, VB5 and VB6 and VB.Net2002 apps.
>
>Is using an unsupported tool the latest and greatest? Nope. Does it work? yup.
>
>Is this tangential fodder for your FUD campaign? Yup.
>
>When does VB6 go unsupported? When does VB.Netxxxx go unsupported? They all go unsupported at some number of years after their initial release. please note these are purely rhetorical questions to provide a realistic counterpoint to your equally absurd FUD statements.
>
>I do not make recommendations for people to ever start development in prior releases of any language be it VFP or VS.Net.