DbSchema points at a folder of DBF files, reads the field definitions straight from each file header, and treats every file as a table — so data from dBASE, FoxPro, and Clipper becomes something you can diagram, query, and document without the original software.
Trusted by teams at
The DBF format started with dBASE in the 1980s and spread through FoxPro, Clipper, and Visual FoxPro. Point-of-sale systems, government agencies, and industrial equipment still read and write these files — while the tools that created them get harder to find every year.
DbSchema gives that data a present-day workflow: field definitions on a diagram, records behind a SQL editor, and a documented structure the next maintainer can actually study.
Everything a rescue or migration project needs, from first look to final mapping.
Field names, types, and widths are read from each DBF header and laid out on the canvas — the data model of a legacy application, recovered without its development environment.
Answer ad-hoc questions about a legacy dataset in the SQL editor and export results — no dBASE syntax, no vintage runtime, no data conversion first.
DBF files share key fields, not declared relationships. Drag the files together in the visual builder, pick the matching columns, and read the generated SQL.
Export the recovered structure as interactive HTML5 documentation — searchable diagrams, field definitions, and comments in any browser. Compliance reviewers and migration contractors get the full picture without touching a single legacy install.
Explore the Documentation Tool
Register either the xBaseJ or the JDBF JDBC driver JAR in DbSchema's driver manager —
DbSchema's own open-source DBF JDBC driver is also available on
GitHub. The URL takes the form
jdbc:xbase:/path/to/directory, pointing at the directory that holds the
.dbf files; each file becomes a table, with Character, Numeric, Date, Logical, and
Memo fields mapped to SQL types. See the DBF JDBC driver page
for setup details.
Two cautions for FoxPro-era files: CDX compound indexes need a driver version that supports
compound index files, since some drivers silently skip indexed records otherwise, and memo
fields stored in external .dbt or .fpt files likewise require a driver
that handles external memo storage.
Free Community Edition — no account, and the 15-day Architect trial is in the box.
Teams working with dBASE / DBF Files often use these engines too. Explore dedicated guides and JDBC setup for each.