Convert DBF to TSV
Turn DBF documents into TSV. One TSV with the field names as the header, dates as YYYY-MM-DD and logical fields as TRUE or FALSE, decoded with the code page the file names, or as Western European when it names none.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop DBF files on the dialor turn it to pick what to do
A dBase table as plain tab-separated text.One TSV with the field names as the header and one row per record.
What you get
A single TSV file. The first row holds the field names. Dates are written as YYYY-MM-DD, and logical fields are written as TRUE or FALSE.
Text is decoded with the code page the DBF file names. When the file names none, it is read as Western European.
Cells that hold a tab, a quote or a line break are quoted.
What does not carry over
Some FoxPro fields are not supported. Currency, date-time and memo fields come out as an unsupported-field note instead of their values. Double fields come out as 0.
Going back
To turn a TSV into a table again, use TSV to DBF.
DBF and TSV.What each format is.
The formats
dBase Table
dBase tables, the attribute tables of shapefiles and many legacy databases.
- Extensions
- .dbf
- MIME type
- application
/x -dbf - Kind
- Documents
Tab-Separated Values
Tab-separated values.
- Extensions
- .tsv .tab
- MIME type
- text
/tab -separated -values - Kind
- Text and data
In your code.The same DBF to TSV conversion through the API, for your app or your agent.
$ cv convert sheet.dbf sheet.tsv$ cv convert sheet.dbf sheet.tsvQuestions.What people ask about DBF to TSV.
Dates are written as YYYY-MM-DD. Logical fields are written as TRUE or FALSE.
The code page named in the DBF file. If the file names none, the text is decoded as Western European.
FoxPro memo, currency and date-time fields come out as an unsupported-field note, not as values.
They come out as 0.