The majority of county boards of elections in Ohio are using a voter registration management application that is still written in Visual FoxPro (and still uses DBF files as the back-end).
Aside: It has a recently-added ToTP implementation that replaces their prior "scan a barcode" system of "two factor" authentication. Of course, you can just open the DBF files directly in another tool and manipulate them w/o any "authentication". The mind boggles.
Direct DBF manipulation is small potatoes. Since the database container (.DBC) has to be writable to be of much use, use that same tool to add some triggers that will run whatever FoxPro code you want (which can call just about any Win32 API you want). If you’ve got FoxPro installed, skip the hex editor and open the DBC like a table (it is a DBF). If one is going to use DBFs, skip the database container feature if you can. It was a good idea maybe 25 years ago (umm, not really), but it was a different time and long before Microsoft started getting their security shit together.
Still using it, but most of our major applications have been ported to .NET / SQL Server.
That being said, still some 50+ smaller / departmental style applications that continue to work, and will likely keep running in their current form for the next 10+ years.
In fact, someone asked me a random foxpro question in the middle of typing this comment haha.
Tell that to the thousands of businesses still using it.
https://www.indeed.com/jobs?q=foxpro