DBF is a family, not one frozen specification
dBASE popularized the DBF table format, and FoxBASE, FoxPro, Visual FoxPro, Clipper and other xBase tools extended or reimplemented it. They share a recognizable header-and-record model, but differ in version signatures, field types, memo files, code pages, indexes and database-level features. A program that supports one DBF generation may misread another while still showing the same extension.
Differences that affect real recovery work
| Area | dBASE lineage | FoxPro / Visual FoxPro | Clipper applications |
|---|---|---|---|
| Memo companion | Usually DBT, with version-dependent layouts | Usually FPT with explicit block information | Often DBT, but driver choice can vary |
| Indexes | IDX and later formats | IDX or compound CDX | NTX is common; replaceable drivers add alternatives |
| Extended types | Varies by generation | Currency, DateTime, Integer, Double, Varchar and binary-capable types may appear | Often traditional dBASE-like fields plus application conventions |
| Code pages | DOS and Windows variants | Language-driver marks and Windows-era data are common | OEM CP437/CP850 and regional encodings are frequent |
| Database metadata | May exist outside a standalone table | DBC containers can hold relations, long names, rules and views | Relations often live in application code |
Why field interpretation matters
A traditional character field is relatively portable, but even it depends on encoding. Numeric and float-like fields may use textual representations in older layouts, while Visual FoxPro can store binary numeric forms. DateTime, currency and auto-increment features need format-aware decoding. Memo-like fields require the correct companion and pointer rules.
Do not map fields based only on their displayed values. A column containing digits may be a character identifier designed to preserve leading zeros. A blank logical value may mean unknown rather than false. Deleted-record markers are record state, not an ordinary user column.
A compatibility checklist
- Identify the version signature and field descriptors before loading the full table.
- Preserve every companion and index file from the same backup generation.
- Verify memo values, code-page behavior and nontraditional field types.
- Compare physical row count, deleted rows and business totals with source reports.
- Document features that a standalone DBF cannot carry, including relationships and validation rules.
DBF Viewer Pro supports common dBASE, FoxPro and Visual FoxPro variants for local inspection, but unusual drivers and damaged files still require evidence-based testing. Start with the memo file guide for external text, or use the Clipper workflow for DOS-era application archives.