The short version
ACCDB vs MDB comes down to age: .mdb is the Access format up to Access 2003, and .accdb has been the default since Access 2007. The extension can lie, the file header cannot: byte 0x14 of the file holds the engine version, 00 for Jet 3 (Access 97), 01 for Jet 4 (Access 2000 to 2003) and 02 or higher for ACE (Access 2007 and later). mdb-ver from mdbtools reads that byte for you. .accde is an .accdb with the VBA source compiled out and forms and reports locked, and .laccdb (or .ldb next to an .mdb) is a lock file, safe to delete only when nobody has the database open.
How to tell which Access format a file really is
Three files from the mdbtools project's test data repository and our own test fixture, one of each generation. The first 0x20 bytes with xxd:
$ xxd -l 0x20 nwind.mdb
00000000: 0001 0000 5374 616e 6461 7264 204a 6574 ....Standard Jet
00000010: 2044 4200 0000 0000 b56e 0362 6009 c255 DB......n.b`..U
$ xxd -l 0x20 DateTestDatabase.mdb
00000000: 0001 0000 5374 616e 6461 7264 204a 6574 ....Standard Jet
00000010: 2044 4200 0100 0000 b56e 0362 6009 c255 DB......n.b`..U
$ xxd -l 0x20 ASampleDatabase.accdb
00000000: 0001 0000 5374 616e 6461 7264 2041 4345 ....Standard ACE
00000010: 2044 4200 0200 0000 b56e 0362 6009 c255 DB......n.b`..U
Two things differ. At offset 4 the two .mdb files say Standard Jet DB and the .accdb says Standard ACE DB. That string is what I observed in these files; the mdbtools format notes do not describe it. The documented field is one byte later in the second line:
$ xxd -s 0x14 -l 1 nwind.mdb
00000014: 00
$ xxd -s 0x14 -l 1 DateTestDatabase.mdb
00000014: 01
$ xxd -s 0x14 -l 1 ASampleDatabase.accdb
00000014: 02
The mdbtools HACKING notes, the project's write-up of the file format, say page 0 is the database definition page and "Offset 0x14 contains the Jet version of this database": 0x00 Jet 3, 0x01 Jet 4, 0x02 Jet 5 (Access 2007), 0x03 Access 2010, 0x04 Access 2013, 0x05 Access 2016, 0x06 Access 2019. The library reads exactly that byte when it opens a file, in src/libmdb/file.c, and refuses anything outside the list with Unknown Jet version.
The same notes give the other big difference: pages are "2K in size for Jet3 (Access 97) and 4K for Jet4". You can see it in the files. Page 1 of the Jet 3 file starts at 0x800; in the Jet 4 file 0x800 is still inside page 0, and page 1 starts at 0x1000, as it does in the ACE file:
$ xxd -s 0x800 -l 8 nwind.mdb
00000800: 0101 b006 0100 0000 ........
$ xxd -s 0x800 -l 8 DateTestDatabase.mdb
00000800: 0000 0000 0000 0000 ........
$ xxd -s 0x1000 -l 8 DateTestDatabase.mdb
00001000: 0101 640f 0100 0000 ..d.....
$ xxd -s 0x1000 -l 8 ASampleDatabase.accdb
00001000: 0101 640f 0100 0000 ..d.....
The leading 01 is the page type, which HACKING lists as a data page.
The file command on macOS is no help here. It calls all three Microsoft Access Database.
mdb-ver: the one-command answer
mdb-ver prints the name for that byte. Its manual page maps JET3 to Access 97, JET4 to Access 2000, XP and 2003, and ACE12, ACE14, ACE15, ACE16 to Access 2007, 2010, 2013 and 2016. The source also prints ACE17 for the Access 2019 value, which the manual does not list yet.
$ mdb-ver --version
mdbtools v1.0.1
$ mdb-ver nwind.mdb
JET3
$ mdb-ver DateTestDatabase.mdb
JET4
$ mdb-ver ASampleDatabase.accdb
ACE12
Renaming does not change the answer, because the extension is not in the file:
$ cp nwind.mdb renamed.accdb
$ mdb-ver renamed.accdb
JET3
Two limits, both from the manual's BUGS section: it "does minimal checking on the validity of a file", and it does not recognise Access 2.0 (Jet 2). I checked the first one. A CSV renamed to .mdb is refused, but a file of 4096 zero bytes passes, because byte 0x14 is 00:
$ mdb-ver notaccess.mdb
Error: unable to open file notaccess.mdb
$ head -c 4096 /dev/zero > zeros.mdb
$ mdb-ver zeros.mdb
JET3
So JET3 on a file you know nothing about only means the header did not object. Try to list its tables before you believe it. More on the rest of the toolkit in Reading .mdb files on Mac and Linux with mdbtools.
ACCDB vs MDB: what each format supports
From Microsoft's Which Access file format should I use? and the Access section of the Office 2007 file formats reference:
.accdb |
.mdb |
|
|---|---|---|
| Default in | Access 2007 and later | Access 2003 and earlier |
| Multivalued lookup fields | Yes | No |
| Attachment data type | Yes | No |
| Calculated data type | Yes, from Access 2010 | No |
| Append-only Long Text (Memo) history | Yes | No |
| Replication | No | Yes |
User-level security (.mdw workgroup files) |
No | Yes |
| Opens in Access 2003 or earlier | No, not even as a linked table | Yes |
| Lock file | .laccdb |
.ldb |
| Compiled, locked version | .accde |
.mde |
Microsoft's advice on that page is to save in .accdb "in most cases", and to leave the file as .mdb if you rely on a feature .accdb dropped. It also says .accdb encryption uses the Windows Crypto API by default. On user-level security it adds that the method is "no longer effective for data security", so that alone is a weak reason to stay on .mdb.
The link direction is one-way too. The 2007 reference says an .accdb can link to tables in an .mdb, but "you cannot link from an .mdb database to tables in an .accdb database."
ACCDB vs ACCDE: what is an .accde file?
An .accde is an .accdb saved "with all of the VBA code compiled", and Microsoft's deployment page says "No VBA source code remains". The Hide VBA code from users page lists what the person holding it cannot do: view or change the VBA, create or modify forms, reports or modules, or import and export forms, reports and modules. They can still update data and run reports. The 2007 reference calls it the Access 2007 version of .mde, "a locked-down version of the original .accdb file".
There is no way back from .accde to an editable design. Microsoft's advice is to keep the original .accdb and make a new .accde from it after each change. If someone hands you only an .accde, the data is still in it (Microsoft says its users can still update data); the forms, reports and code are what you cannot get back. I had no .accde to test, so I make no claim here about reading one outside Access.
.accdr is a different thing: the same .accdb with the extension changed so Access opens it in runtime mode. Renaming it back to .accdb "restores full functionality", per the 2007 reference.
What is a .laccdb file, and can I delete it?
It is the lock file. Microsoft's description of Access lock files says one is created for every database "opened for shared use", with the same name in the same folder: open Northwind.accdb and Northwind.laccdb appears beside it. .laccdb goes with .accdb, .ldb with .mdb. It holds a 64-byte entry per user, the computer name and the security name, and is never larger than 16 KB. No table data is in it.
Access deletes it when the last user closes the database. It stays behind in two cases the page names: a user without delete rights on the folder, or a database marked as corrupted, where the file is kept on purpose because it records who was in at the time. Opening with Open Exclusive skips the lock file altogether.
So it is safe to delete when nobody has the database open. If someone does, it is the file that tells the engine whose record is locked, and the page also warns that entries are not removed on close, so the names inside are not a reliable list of who is in now. A leftover .laccdb you are sure is orphaned can go. The same page says the state of the lock file "has no bearing on the state of the database", so one that arrived in a zip next to the database can simply be left out. mdbtools does not create one: after every run above, the folder held only the files I put there.
Can I convert ACCDB to MDB, or MDB to ACCDB?
Only Access itself does this as a true format conversion. I have no copy of Access on this machine, so the steps below are Microsoft's, not something I ran.
MDB to ACCDB, per Convert a database to the .accdb file format: open the Access 2000 or 2002-2003 .mdb in Access 2007 or later, then File, Save As, Save Database As, choose the Access file type, and save. Access writes a copy and leaves the .mdb alone. An Access 97 file (the JET3 kind) is harder: "Starting with Access 2013, it's no longer possible to directly convert an Access 97 database". The page's route is to open it in an earlier version such as Access 2003, save it in a newer .mdb format, then convert that.
ACCDB to MDB, per Convert an .accdb database to an earlier file format: File, Save As, then Access 2002-2003 Database or Access 2000 Database under Save Database As. It refuses if the database uses anything the old format lacks: multivalued lookup fields, Attachment fields, Calculated fields, append-only Long Text, links to .accdb, .xlsx or SharePoint tables, or a database password. Those have to come out first. Getting to Access 97 takes a second step in an older Access.
So an "accdb to mdb converter" that runs without Access cannot be doing this. What a tool outside Access can do is read the tables out of either format.
Reading all three formats without Access
The ACCDB to CSV converter on this site takes .mdb and .accdb the same way, through mdbtools, which handles Jet 3, Jet 4 and ACE. I pushed the three files through its Python reader and CSV writer (READERS["access"], then WRITERS["csv"]) and counted the rows it produced per table:
== nwind.mdb: 9 tables
Order Details: 2155 rows
Orders: 830 rows
Products: 77 rows
Shippers: 3 rows
Categories: 8 rows
Customers: 91 rows
Employees: 9 rows
Suppliers: 29 rows
Umsätze: 830 rows
== DateTestDatabase.mdb: 1 tables
DateTest: 6 rows
ACCESS_DATE_DECODED: DateTest: 8 date value(s) in DateCol, DateTimeCol, TimeCol are valid Access dates that mdbtools could not print (it printed '1900-01-00'). They were decoded from the stored value instead.
== ASampleDatabase.accdb: 1 tables
Asset Items: 65 rows
mdb-count agrees on the ones I checked (2155 for Order Details, 91 for Customers, 65 for Asset Items). The Jet 3 file is the one to watch for text: the mdb-ver manual notes Jet 4 "added support for unicode", and mdbtools reads Jet 3 text as CP1252 unless told otherwise. The Northwind customer names came out as UTF-8 with their accents intact:
$ grep -m2 "[äöüéñ]" Customers.csv
ANATR,Ana Trujillo Emparedados y helados,Ana Trujillo,Owner,Avda. de la Constitución 2222,México D.F.,,05021,Mexico,(5) 555-4729,(5) 555-3745
ANTON,Antonio Moreno Taquería,Antonio Moreno,Owner,Mataderos 2312,México D.F.,,05023,Mexico,(5) 555-3932,
The ACE file's first row, with the date in ISO form and Currency keeping four decimals:
$ head -2 "Asset Items.csv"
Asset No,Asset Category,Make,Model,Description,Owner,Serial No,Acquired,Cost,Warranty,Tax Scale,Supplier No,Comments
30050,Computer Hardware,GEO Rocket,220ZX,Computer,Sales,344-667,1997-09-02 00:00:00,1995.5000,12,A,44577,
The renamed renamed.accdb (a Jet 3 file) read the same nine tables. Which format you have matters less for getting the data out than for staying in Access: it decides which Access versions can open the file, and whether it can hold .accdb-only types like attachments. Dates are where Access files bite, and Open an ACCDB or MDB file without Microsoft Access walks through those and the Windows routes.
Sources
- Which Access file format should I use?, Microsoft Support
- File formats supported in the 2007 Office system, Microsoft Learn
- Description of Access lock files (laccdb and ldb), Microsoft Learn
- Deploy an Access application, Microsoft Support
- Hide VBA code from users, Microsoft Support
- Convert a database to the .accdb file format, Microsoft Support
- Convert an .accdb database to an earlier file format, Microsoft Support
- MDB Tools: HACKING notes, mdb-ver manual, file.c, mdb-ver.c
- mdbtestdata, the MDB Tools project's test databases