>>>I say that VFP9 will still run on the version of Windows 10 that is the most recent one in 2030.
>>
>>I don't know if VFP9 will run that updated Windows 10 at 2030, but I know one thing there will be less more and less classical Windows applications in next a few years. Microsoft pushes to us Windows store applications. There is a project by Microsoft to generate Windows Store applications. MS supports us and a guy from MS calls me every week about that project.
>
>I too have seen the videos about APPX (http://en.wikipedia.org/wiki/APPX). It will have full support for Win32 applications because it will also include all Win32 APIs. That is really good news. It implies that we are now able to migrate in a slow pace. All our current applications can be run as Appx and be sold in the Windows Store. And future developments can be done either in VFP or with the help of other languages/platforms or a mix. In theory, there's no need to convert anything. That was a different story when we went from FPD to FPW to VFP.
>
>So, I side with Tore Bleken that we can be sure that our apps will work till at least 2030 and that we'll even be able to use the Development Environment and the language to develop new stuff. And VFP is still among the fastest dbms'es.

Using APPX to distribute a VFP app via Windows Store and via that route run under Windows 10 is not the same as saying your VFP app will run under Windows 10 natively. If you don't include the qualifier that you're using a virtualization tool then you can also claim your VFP app runs on Linux and Mac.