// blog

Moving a Visual FoxPro Program to the Web: DBF Tables, Reports and Rules

A Visual FoxPro program moves to the web in four parts: its DBF tables, with their CDX indexes and FPT memo files, are read and imported into PostgreSQL with record counts and totals checked; the rules in .prg files and form methods are written down and built once on the server; forms and grids become web screens with the same columns and shortcuts; and FRX reports become print pages and PDFs.

Last updated 1 min read

The start of an old FoxPro table file, shown as bytes

Visual FoxPro programs run inventory, billing and job tracking in more businesses than you’d guess. They’re fast and they’ve been reliable for decades. The trouble is finding someone to change one. Here’s what moving one to the web involves.

The data comes first

FoxPro keeps its data in DBF tables, with CDX index files and FPT memo files beside them. We read the tables with their memos and import them into PostgreSQL. Then we prove it: record counts and totals in the new database are checked against the old program before anyone switches.

The rules

FoxPro code lives in .prg files, in form methods and in classes. That’s where the rules are: how a price is worked out, when an order can ship. Each one is written as a plain sentence, checked by the people who use the program, and built once on the server.

Screens and reports

Forms and grids become web screens with the same columns and keyboard shortcuts. FRX reports and labels become print pages and PDFs that look the same.

What we check first

Free tables versus a database container, reports and labels, ActiveX controls and anything plugged in, like scanners or label printers. They’re all listed before the price.

The same method moved two real desktop programs to the web, Virtual Salesman and TurboCASH. See how a FoxPro program moves to the web. The first call is free.