Video: Import data from CSV file into DBF table in a few clicks

This video shows how to import data from CSV file into DBF table in a few clicks with Withdata FileToDB, or with the free Import CSV into DBF online tool. It covers the CSV side and the dbf side.

Convert CSV to DBF: what this does

This shows how to turn a CSV file into a DBF (dBase) table — usually because a legacy dBase, FoxPro or Clipper application expects .dbf files. The video above is the full flow; the notes cover the DBF-specific details.

Steps

Open Withdata FileToDB and pick the CSV file.
Choose DBF as the destination.
Confirm the field mapping and the character encoding (code page) before writing.
Create the table or append to an existing .dbf.
Run the import.

CSV to DBF: details worth knowing

Encoding has no marker. A DBF header records no code page, so you must pick the right one — otherwise accented or non-Latin text comes out garbled.
Field names are limited. Classic DBF field names are capped at 10 characters, so long CSV headers are truncated (plan the target names first).
Field widths matter. DBF is fixed-width per field: choose the numeric width and decimal places so large values are not silently truncated.
Long text goes to a Memo field. Text longer than the character limit needs an M field, stored in a separate .dbt file that must travel with the .dbf.
Dates. DBF stores dates as YYYYMMDD, so date columns should be mapped to a real Date field rather than left as text.

FAQ

Why are my column names cut short?: Classic DBF allows only 10 characters per field name.
Where does long text go?: Into a Memo field, stored in a companion .dbt file.
Accented characters look wrong — why?: Pick the matching code page; DBF does not record which one it uses.

See the tool page Convert CSV to DBF, or the app overview Withdata FileToDB.

Download Withdata FileToDB