Convert FoxPro to CSV

Working from a FoxPro table

FoxPro extended the dBase file layout with types dBase never had, and gave its memo files a different format and a different extension. Both of those differences change what comes out the other side, and both are read from the file.

• →The FoxPro-only field types are read as themselves: Currency (Y) becomes an exact decimal rather than a float, Integer (I) a 64-bit integer, DateTime (T) a timestamp, Double (B) a floating-point number.
• →Memo text is expected in a .fpt, chosen from the Visual FoxPro and FoxPro 2.x version bytes 0x30, 0x31, 0x32, 0xF5 and 0xFB, rather than in the dBase .dbt.
• →Only the .dbf itself is read. A table bound to a Visual FoxPro database container keeps its long field names and relations in the .dbc, so columns arrive under the short names in the table header.

The shape of the CSV files you get

CSV is where the type information stops, so what is left to describe is the file itself: how a row is terminated, which fields are quoted, and how a value that used to have a type is spelled out as characters.

• →Rows end with a carriage return and a line feed, the RFC 4180 ending, while a newline inside a quoted field stays the single character it always was. The encoding is UTF-8 with no byte-order mark in front of it.
• →Quotes go on only where they are needed - a field holding a comma, a double quote or a newline - and a quote inside a field is doubled rather than escaped with a backslash. Every other field is written bare.
• →Decimal values are written digit for digit and never through a floating-point number, so a money column that was exact in the source is still exact in the file. Booleans are written lower case, as true and false, which is the spelling this converter's own reader takes back as a boolean.

Reading FoxPro

• →Numeric fields with decimals are read as exact decimals, not floats, so currency does not drift.
• →Character field widths are read from the header and carried into the target.
• →The code page declared in the file header is used, so Cyrillic, Western European and other legacy DOS encodings decode correctly instead of turning into mojibake. 157 code pages are recognised.
• →Files written by dBase III or Clipper declare no code page at all — the header byte for it did not exist yet. For those, the most plausible encoding is chosen by inspecting the text, and the conversion tells you it had to guess. The API takes a sourceEncoding parameter (e.g. cp866) to force it instead of guessing, though the widget above does not have a control for it yet.
• →Memo columns keep their text in a separate .dbt or .fpt file. If the .dbf declares one and it was not uploaded, the conversion stops and tells you which file to add, rather than handing you a table whose long text is silently blank.

Writing CSV

• →One file per table, with a header row.
• →NULL is written as an empty field, never the word "None".
• →Binary data is written as hex, which is reversible.

Convert FoxPro to something else

• MySQL
• PostgreSQL
• Oracle
• SQL Server
• SQLite
• DuckDB
• Excel

Convert something else to CSV

• Excel
• SQLite
• SQL dump
• JSON
• XML
• Parquet
• DuckDB
• MS Access
• PostgreSQL backup