Microsoft killed FoxPro in 2007. Anyway, here's FoxPro revived

Your FoxPro applications, at home on a modern machine. FoxDev Studio opens the projects, forms and tables you already have and runs them the way you remember: no rewrite, no conversion, no export step . Download Get started How it is built Customer Company Western Trading Co. Credit limit 25,000.00 Save It picks up where you left off Point it at a folder you have not opened in years, and what is there is what you get. Your project, as it is Projects, forms, class libraries, menus and reports open straight from the files you already have. Nothing is migrated first, and nothing is left behind. The designers you know Forms, classes, menus and reports are edited where you expect them to be, alongside the project manager, the Command Window and a debugger that stops on your line. Your data stays your data Tables, indexes, memos and databases are read and written in place. What sits on disk afterwards is the same kind of file it was before. Whatever it talked to, it still talks to The system calls, the automation objects and the old add-in libraries your application leans on keep working, so the parts nobody wants to touch stay untouched. What it looks like The IDE, on Visual FoxPro's own sample projects. Every picture is a real session. Visual FoxPro's own Solution sample, imported and running: its launcher form on the Screen tab, the project's 123 forms, 7 menus and 11 class libraries in the explorer, and the runtime waiting for events. The editor lints through the runtime's own compiler, so what it underlines is what would fail. Stopped one step past a breakpoint in the Solution sample's main program: call stack, locals, watches, and the line it is on. A database container in the table browser: 8 fields, 17 records, memos a click away. FoxScript: lambdas answering HTTP routes, a 32-bit library called from inside one, listening on 8080. Built to match, not to approximate Small differences are what break an old application: a number printed a column too wide, an event arriving a moment late, an error with the wrong number on it. So behaviour here is settled by asking Visual FoxPro itself and matching its answer, rather than by reading a reference page and hoping. What comes out of that is a runtime written from scratch: quick to start, self-contained, and straightforward about the corners it has not reached yet. 1,722 elements of the Visual FoxPro 9 language reference known to the runtime 1,534 of them exercised by a test that compares the answer with the product's 3 names it has not met yet; everything else runs, is ignored on purpose, or is refused by name What Visual FoxPro 10 would have been Visual FoxPro stopped at version 9, and at 32 bits. This is the same language, rebuilt on a foundation that has not been frozen since 2007. Four pieces are what make that possible. Where a call goes / and where the 32-bit world stops 64-BIT 32-BIT The form on screen React, drawing straight from the tree below repaints one control, not the form The live object