.dbf

Project Vulcan – CP/M (Level 1)

There is no publicly available information on the original layout. What is known is that it was a simple table which allowed adding, deleting, modifying, and outputting ASCII data. It was written for 8-bit machines that ran CP/M.

dBASE II – MS-DOS (Level 2)

dBASE II was the first major release by Ashton-Tate. It had many advancements beyond the simple table structures of Project Vulcan.[2]

• Still written for 8-bit computing
• Increased the number of fields from 16 to 32
• Introduced a SORT routine
• 16-bit version finally released in April 1983 (version 2.4)

dBASE III – MSDOS (Level 2sh)

dBASE III (version "1.0"), was released in June 1984. This was a fully 16-bit application. dBASE III's file format is a transitional step between dBASE II and dBASE III+.

dBASE III+ – MS-DOS (Level 3)

dBASE III+ was released in December 1985. It ushered the modern dBASE file format. It is incompatible with dBASE III's file format.[3]

dBASE IV – MS-DOS (Level 4)

• 1.0 x322 Oct 1988
• 1.0 x55 Mar 1993 – dBASE Compiler
• 2.0 x12 Oct 1993 Includes fixes in dBASE IV v2.0 x16 above (not x17 i.e. not VLM compatible, dB5D exe's are compatible). It's also a new version that contain new features not in the V1.0 product:
  • 32-bit generation
  • Auto compiling and linking
  • Smaller .EXE size
  • Menu-driven user interface
  • Linker can produce combined .DBO output
  • Linker can produce a .MAP file
  • Compiler supports alternate date formats
  • command-line switches accept wildcards in file names.

dBASE V – MS-DOS (Level 5)

1.0 x46 Jun 1994

BDE – Borland Database Engine 2.52

This was the last update to the 16-bit version of the Borland Database Engine (BDE).[4]

dBASE V – MS-Windows (Level 5)

• 5.5 b673 Jul 1995

xBase is a name applied to clones of the dBase, typically dBASE III+–V. Most xBase programs either use the format directly or uses a derived format with custom extensions. Erik Bachmann maintains an open-licensed description of these formats.[5]

The Level 7 structure is the latest supported by dBASE and BDE. It is incompatible with the previous file format, and is supported by few third-party applications.[6]

dBASE 7 – MS-Windows (Level 7)

• 7.0 b1345 Dec 1997 Full 32 bit version for Win 95/NT

Level 7 brought many improvements. The maximum length for field names increased from 10 to 31 characters. Some new fields types were added, such as the auto-increment field,[7] which prevents creation of duplicate record numbers in the same table.

BDE version 5.1.0

Significant improvements over the prior releases.[8] There are also some limitations with regards to what the BDE can handle.[9]

Each record begins with a 1-byte "deletion" flag. The byte's value is a space (0x20), if the record is active, or an asterisk (0x2A), if the record is deleted. Fields are packed into records without field separators or record terminators.

All field data is ASCII. Depending on the field's type, the application imposes further restrictions:

A memo (.DBT) file consists of blocks numbered sequentially (0,1,2, and so on). SET BLOCKSIZE determines the size of each block. The first block, block 0, is the memo file header.

Each memo field of each record in the .DBF file contains the number of the block (in ASCII) where the memo field begins. If the memo field contains no data, the .DBF file contains blanks (0x20) rather than a number.

When a memo field's content changes, its block number may also change. I.e. the memo gets relocated. In that case, the number in the .DBF file gets updated.

In dBASE III PLUS, the space consumed by deleted text in a memo field cannot be reused — the .DBT file size grows each time text is added, even if other text has been deleted. dBASE for DOS may reuse that space for new text. dBASE IQ PLUS always appended new text to the end of the .dbt file.