>Also VFP's native DB engine is blisteringly fast on all but the most complex data usage. For any mid-range app, it is the tool I would choose unreservedly. Smaller apps, possibly. Very large apps, would depend on many factors.
>VFP9 works. FPW 2.6 still runs in Win7 32-bit mode. VFP9 will likely run 20+ years on x86-64.
>It is odd to me people want to abandon such a powerful tool as VFP because MS stopped supporting it. Many other people and projects are.

ISAM-file type of DB access running into SMB2 errors are IMO a reason to be forced off that type of programming.
Seeing the side benefits DB servers offer (some of them free and not only without cost) that switch makes sense in todays environment.

Yes vfp hits a sweet spot with 80% of needed GUI controls, dynamic typing reducing code size and local cursors.
But it isolates you in Win32 as well. Maybe Lianja will take care of isolation and enhance other aspects -
but I can make a good case for python or JS development and can also work in Java or Dotnet with a framework.

"still runs" is good enough IMO for maintainance and day2day enhancement - but not for new projects,unless they are thow-away.