>
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.
>

I am not saying that...rather, I am saying that you are placing WAY too much emphasis on the fact that MS will support Fox until 2010.

Obvioiusly, apps won't break - but the app platform in all material respects is dead.


>
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.
>

I agree - I don't see your point here.


>
Is using an unsupported tool the latest and greatest? Nope. Does it work? yup.
>

It would be rather unwise to advise a client to adopt an unsupported tool just because it can get the job done. And, it would be unwise to advise a client to stay with what is now unsupported just because it gets the job done.

>
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.
>

Interesting...so what you are saying is that it is OK to be unrealistic about a vendor supporting a product until 2010 - because it is not "negative". You say I am guilty of spreading FUD. I say your P.C. cup runneth over...