A bit more solely about VFP:
After the end of VFP MS open sourced some parts of VFP10 written in VFP also working with VFP9 and called that the Sedna Add-On. They published it on codeplex (which now itself has ceased to exist) and the VFP community added to that what was soon called VFPX for obvious reasons. There you have your answer about new development since 2007. Most things are in VFPX and now moved and still moving from codeplex to
Edit: There was a misunderstanding mostly in the industry and press not knowing VFP that Sedna realse meant MS open sourced VFP, but that's nonsense. Many tools within the VFP IDE already were VFP code itself even in VFP6, you always had the xsource.zip giving you source code of wizards and more.
Technologies, which work "with VFP", well, there is no migration tool or path from MS and no other company really made an effort to do so. There are some to me questionable things I won't even mention and maybe the best effort to keep VFP code alive by porting the runtime is Christof Wollenhaupts Guineu. Maybe I am biased for knowing him personally, but this thing also is stuck and not a main product. He extends it as necessary to support his projects and most things are solved for him, which means only a limited subset of the VFP language is supported. I would recommend to forget about continuing with this language with some compatible successor. Go with the flow, means go with current trends and that is - as unfortunate as it is - mainly JavaScript and all the tools and frameworks done with it. Very fortunately having the great jQuery backbone.
I don't know where you came from before you started VFP, was it databases or was it even the way of enabling to write and execute small scripts including any DOS/SHELL commands via RUN, that brought you to VFP? When you say you went system administration, I think Powershell is for you. Not only because the latest meeting of a regional developer group including Christof Wollenhaupt was with a session about Powershell. It is in very short iving you all.NET Framework and more at the commandline and supersedes both the normal Windows cmd.exe Shell and WMI for acting on most anything OS related even including GUI.
Recent Ransomware attacks make Powershell a target to be turned off, but I also see Ransomware detection, protection and removal supported with Powershell scripts. It is just logical that the most comprehensive language available on any Windows machine is used by Malware. MS and more so Secret Services and Governments should learn from this, that there is no beneficial use of kept secret exploits. MS will make it even safer to execute only signed and encrypted scripts and this way may make Powershell the safest way to execute only trusted applications.
OK, that was leading off topic to Powershell. Last, not least you should consider reading the "What's New in X"-books, which Hentzenwerke published for VFP7, 8 and 9. If you even left before VFP6, then you may really start from scratch and take some learning resources from
I think this overall covers you for now.
Bye, Olaf.