Hi, Pertti

>[snip] I've said it before here and will say it again: the very moment the VFP runtime libraries are partially or completely broken by a new version of Windows (happened to VFP3 and FPM 2.6 with Mac OS X on the Mac side) or by a leap in computer hardware infrastructure (happened with FPW 2.6 and new "speed demon" Pentiums running over 300mHz (sic!) ) or by another mission critical Windows program trompsing all over VFP, the game is over. If nobody's at the factory to adjust the core product to the changing environments, any and all "open source" additions become immediately useless along with the millions of VFP -based applications around the world.

There is still a long support period, and if some problem of that importance happens in that timeframe, then a fixed will be most probably provided, even if it is a patch like the one they released for the old FPW 2.6.

As for the short-term, the SP 2 will target all the identified Vista-related issues. I really can't see why it seems SO dangerous that a very stable product, which successfully resisted several platform revamps is not expected to be upgraded at the core.

I was always amazed at the amount of VFP developers that are still using prior versions, or don't have the latest SPs applied. Not to mention again all the FPD applications still alive and kicking.

How may people tried or incorporated some of the excellent extensions already available in the VFP X projects?

Don't panic, please, people. We all feel emotional about this product, but let's keep things in perspective.

Regards,