>>Yes, there will still be Fox apps running in 5 years and even further. Note I referenced the U.S. in my original reply, as I recognize Fox is more popular in other countries right now.

My Fox isn't Fox anymore. As an example, ASM code for encryption and compression now is inlined into my prgs with the vast majority of old VFP code now compiled to C++ with no need for a VFP runtime. Currently experimenting with C++ SQL Server and SQLLite direct access to eliminate ODBC driver snafus. The goal is to allow the customer to maintain a handful of app files and a config file that can be xcopied to literally any desktop with expectation it will just work even if it's a home worker's PC. Other language users may no longer fear the old DLL Hell but still need to worry about large support libraries and all sorts of joy if 2 apps insist on their own library versions. My stuff isn't easy to hack either, because apart from the difficulty making sense of decompiled C++, there's fiendishly clever (not my work!) hack detection using assembly language that few mortals still can pick apart, scattered throughout. Currently I'm seriously investigating 64-bit compilation because the new x64 IDE does seem quicker than the old thunked x86 VFP. Conclusion: in 2017, Xbase code merely is the human-readable first step along the path to C++ dlls.