>Huh? Where do you see that there are future SPs planned for VB 6, VC++ 6, InterDev, or VJ++?

Hey Craig,

Maybe I'm wrong, but didn't Microsoft announce that they would be providing support for VB6 until 2005 and stop total support on 2008 (Not sure if the dates are correct). As I understood it, they would provide updates until 2005 for free and charge a fee for updates until 2008. The reason that they went to named date support instead of past two-version support was because of the greater time between delivery of the versions.

Frankly, I'm a little concerned about the announcement myself.
Will Microsoft be providing fixes for critical issues that arrise in the future?
Plus why stop SP releases on an existing product?

Your comment on MS stopping support on VB6 is a bad comparison. VB6 has been replaced by VB.NET, VFP7 is still a current product with no replacement available for how many months/years?

I could understand stopping support of VFP6 now, but not 7.

MS at least gave VB6 a nice planned lifecycle and said well in advance when support would stop and what support could be expected. So the users could plan out their migration strategy to the next version.

The notice we just received was that there will no longer be any further fixes provided. If MS was serious about supporting Visual FoxPro as they claim, then they would have provided a life-cycle support structure similar to VB, would it not seem so?

Just my thoughts,
Ken