>Since I hear that VFP will run on Win 10, I've pretty much decided to get rid of my XP and get a Win 10 pc... though not sure which version.
>
>What do we do with the thousands of apps out there still running on VFP when a future Win10 update "breaks" VFP and the apps no longer run? I guess I've always been a worrier, but seriously... is there an alternative plan of action or are we all just "screwed"?

The (mostly) enforced updates of Win10 is a significant concern for legacy apps.

One way to protect yourself against that is to run them in one or more virtual machines (VMs). If you install Windows 8.1 or Windows 7 on a VM you'll have a known environment.

Windows 7 end-of-life is 2020.01.14
Windows 8.1 EOL is 2023.01.10

http://windows.microsoft.com/en-us/windows/lifecycle

To support VMs you should get a machine with a modern 64-bit processor with at least 4 physical cores/APUs and at least 8GB RAM. If you get the Pro version of Windows 10, that includes Client Hyper-V which is Microsoft's technology for creating and managing VMs. There are other products available as well, such as the free Oracle VM VirtualBox (which I've used for some time), VMWare Workstation etc.

Some of these products support a physical-to-virtual (P2V) migration. So, you could, for example, do a P2V migration on your existing XP machine, and then run it as a VM on a new Win10 box. That doesn't mitigate the fact that XP is no longer supported and is increasingly vulnerable to web threats, but if you will only be using it occasionally and with limited or zero need to access the public Internet, that may not be an issue.

I have one client where I still need to occasionally run 16-bit FoxPro for DOS. A 64-bit Windows OS can't natively run 16-bit apps so on my 64-bit laptop I installed a 32-bit Windows 7 VM on VirtualBox and run FPDOS from there. Works just fine - in fact, a lot better than the old physical hardware I used to run it on at the client site.