MDB / ACCDB to CSV / SQLite
Extract records & schema from legacy MS Access .mdb/.accdb files — 100% private client-side processing.
Active Converter
MDB / ACCDB to CSV / SQLite: Extracting Legacy Microsoft Access Databases Locally
Technical Anatomy of Microsoft Access .MDB & .ACCDB Files
Microsoft Access stores tables, queries, forms, and indexes inside a single binary container powered by either the Jet Database Engine (.mdb, Access 97–2003) or the ACE Engine (.accdb, Access 2007–2024). Every valid Access file opens with a 4-byte page header (00 01 00 00) followed immediately at byte offset 0x04 by the ASCII signature Standard Jet DB\0 or Standard ACE DB\0.
Internally, the container is divided into fixed-size pages—2,048 bytes in Jet 3 and 4,096 bytes in Jet 4 and ACE. System catalog metadata lives inside MSysObjects, while table definitions (TDEF pages) describe column types and data pages hold UTF-16LE (UCS-2) or compressed ASCII text rows. Extracting records into open .csv or .sql / SQLite formats liberates decades-old business data from Windows-only vendor lock-in.
Raw Jet/ACE Binary Header vs. Extracted CSV / SQLite Output
# Input: Binary Access File Header (inventory_2003.mdb)
00000000: 00 01 00 00 53 74 61 6E 64 61 72 64 20 4A 65 74 |....Standard Jet|
00000010: 20 44 42 00 01 00 00 00 B5 6E 03 62 60 09 C2 55 | DB......n.b`..U|
# Converted CSV / SQLite Export:
CREATE TABLE extracted_records (id INTEGER, payload TEXT);
INSERT INTO extracted_records VALUES (1, 'MSysObjects');
INSERT INTO extracted_records VALUES (2, 'Customers_2003');
Real-World Software & Hardware Ecosystem
Legacy .mdb and .accdb databases remain widespread across medical clinics, small manufacturing ERPs, ESRI Personal Geodatabases, ZKTeco biometric attendance machines (att2000.mdb), and older Visual Basic 6 / .NET desktop software. Technicians migrating away from Access typically move data into SQLite, PostgreSQL, or Microsoft Excel.
Troubleshooting & Edge Cases
- UCS-2 / UTF-16LE Compressed Strings in Jet 4: Access 2000+ compresses Latin text using a leading
0xFF 0xFEmarker inside data pages. If a field contains mixed binary flags, review the extracted rows in Interactive Table view to filter out internalMSys*catalog entries. - 2 GB File Size Ceiling & Corruption: Access databases approaching 2 GB frequently suffer torn index pages. Always work on a read-only copy of the
.mdbfile rather than the live production database. - Workgroup Security (.MDW) Files: Legacy Access 97–2003 files secured with an external
system.mdwworkgroup file restrict table access at the engine layer; unencrypted data pages can still be audited for recovery.
Jet 3 vs. Jet 4 vs. ACE (.ACCDB) Binary Page Comparison
| Engine Version | Header String (0x04) | Page Size & Text Encoding |
|---|---|---|
| Jet 3 (Access 97) | Standard Jet DB | 2,048-byte pages, 8-bit ANSI codepage |
| Jet 4 (Access 2000–2003) | Standard Jet DB | 4,096-byte pages, UCS-2 / UTF-16LE compressed |
| ACE 12–16 (.ACCDB) | Standard ACE DB | 4,096-byte pages, UTF-16LE + Attachment blobs |
Linux / macOS CLI Equivalent (mdbtools)
# List tables and export a legacy Access .mdb table on Linux/macOS:
mdb-tables -1 att2000.mdb
mdb-export att2000.mdb CHECKINOUT > attendance.csv
Frequently Asked Questions
Access 97–2003 .MDB files use the Microsoft Jet Database Engine (header string 'Standard Jet DB' at byte offset 0x04), while Access 2007+ .ACCDB files use the Access Connectivity Engine ('Standard ACE DB') with support for multi-valued fields and attachment columns.
Access databases store data in fixed 2 KB (Jet 3) or 4 KB (Jet 4/ACE) binary pages. Our client-side binary scanner reads the page stream locally to recover readable table records, schema strings, and structured exports to CSV or SQLite-ready SQL.
Yes. Because Microsoft Access is Windows-only, macOS and Linux users routinely convert .mdb/.accdb archives into open-standard CSV or SQLite formats so they can open them in Excel, LibreOffice, or DB Browser for SQLite.
Encrypted Access databases scramble data pages using RC4 or AES-128/256 with the user password. You must first remove database encryption inside Access (File → Info → Decrypt Database) before any third-party tool can read the records.