{"id":3726,"date":"2014-11-18T14:46:01","date_gmt":"2014-11-18T14:46:01","guid":{"rendered":"http:\/\/www.withdata.com\/blog\/?p=3726"},"modified":"2026-09-16T17:21:17","modified_gmt":"2026-09-16T17:21:17","slug":"download-microsoft-access-database-engine-32-bit","status":"publish","type":"post","link":"https:\/\/www.withdata.com\/blog\/tips\/download-microsoft-access-database-engine-32-bit.html","title":{"rendered":"Download Microsoft Access Database Engine (32-bit)"},"content":{"rendered":"

Short answer:<\/strong> the 32-bit build of the Microsoft Access Database Engine 2016 Redistributable is the file AccessDatabaseEngine.exe<\/code> — no _X64<\/code> suffix. You can download it from Microsoft<\/a>.<\/p>\n

Two things are worth knowing before you install it. First, the 32-bit engine is normally the right choice — 32-bit Office is still the default, and most data tools are 32-bit too. Second, it carries a memory limit that shows up as soon as a job gets big, and no amount of reinstalling will remove it. Both are explained below.<\/p>\n

Which build do you actually need?<\/h2>\n

The Access Database Engine ships in two builds and they are not<\/strong> interchangeable. Your application, your Office installation and the engine all have to agree.<\/p>\n\n\n\n\n\n
<\/th>\n32-bit — this page<\/th>\n64-bit<\/th>\n<\/tr>\n
File name<\/td>\nAccessDatabaseEngine.exe<\/code><\/td>\nAccessDatabaseEngine_X64.exe<\/code><\/td>\n<\/tr>\n
Install it when<\/td>\nthe program that reads the database is 32-bit<\/td>\nthat program is 64-bit<\/td>\n<\/tr>\n
Symptom if you pick wrong<\/td>\nthe provider never shows up in the list<\/td>\n“Provider cannot be found” still appears after installing<\/td>\n<\/tr>\n<\/table>\n

Why 32-bit is usually the one people need<\/h2>\n

Microsoft Office installs as 32-bit unless someone deliberately picks the 64-bit option, and that choice has to be made at install time. Most older data tools, reporting add-ins and ODBC clients are 32-bit as well. If the program that reads your Access database sits under C:\\Program Files (x86)<\/code>, it is 32-bit and it needs this engine.<\/p>\n

To confirm on your own machine: in Office, File → Account → About Excel shows the bitness on the first line. For any other program, open Task Manager, go to the Details<\/em> tab and look for the “(32 bit)” label next to the process name.<\/p>\n

The 32-bit ceiling you will run into eventually<\/h2>\n

A 32-bit process can address roughly 2 GB of memory, and the Access engine loads much of its working set inside the calling process. A wide query, or a table with long Text and Memo columns, can exhaust that space even on a machine with plenty of free RAM. The job then fails with an out-of-memory error that looks like a data problem but is really an addressing limit.<\/p>\n

If that is what brought you here, installing this driver will not help. The limit belongs to the 32-bit build itself, and it is the main reason to move the work to a 64-bit tool.<\/p>\n

No driver, and no 2 GB ceiling<\/h2>\n

Withdata’s Access tools open .mdb and .accdb files directly in a 64-bit process, so they never load the ACE provider and never hit that ceiling. No Access Database Engine, no ODBC or OLEDB driver, no Microsoft Access installation — on Windows, Linux and macOS.<\/p>\n