Something to tell clients is to note the dates for when VFP 6.0 'extended' support ended, and that many VFP 6.0 apps are still working fine and in use today, some very large applications (thousands of users each). You can tell them that if VFP doesn't run on an update of a new version of Windows, then all the users of those hundreds of thousands of machines using the VFP runtime can't upgrade to the latest version of Windows - which Microsoft wouldn't want.

And Win7 plus future versions have a compatibility mode (like XP mode) as needed. So I expect VFP 6.0 and later apps will run fine on new versions of Windows for the next 10+ years. I have a very complex FoxPro 2.0 DOS app (the police/fire dispatch app I showed Bill Gates in 1992) that runs in a DOS window on Windows 7 32-bit just fine, I actually did a demo of it to some people last month. So when you show the dates to people, not the past versions that have expired but are still running fine today.

Let me know if this info helps a bit in your efforts in enhancing perception of VFP usage.

>Once Ken Levy posted a mesage on UT regarding the life cycle of VFP and what that meant for the clients. Some client have the impression that because VFP is "dead" it would stop working suddenly after 2015, and I was looking for a good comment (preferably by MS or an employee of MS) that clears up that perception. So if you find the message or know of another statement that I could use to show to the client would be great.