Converting .mdb to .accdb: The Complete How-To Guide
The .mdb format served Access users for over a decade, but .accdb is the modern standard. Here is everything you need to know to convert your database safely — and what to watch out for.
The .mdb file format was the backbone of Microsoft Access from its introduction in 1992 through Access 2003. In 2007, Microsoft introduced the .accdb format as the new default. Today, if you are still running an .mdb database, you are using a file format that is nearly 20 years out of date.
This guide focuses specifically on the file format conversion — what changes, what breaks, how to do it, and when it might make sense to stay on .mdb.
.mdb vs .accdb: What Actually Differs
Understanding the technical differences helps you anticipate what will and will not survive the conversion.
The Database Engine
.mdb files use the Jet database engine (specifically Jet 4.0 for Access 2000–2003). .accdb files use the ACE (Access Connectivity Engine), which is the successor to Jet. ACE is backward-compatible with Jet in most respects but adds new capabilities and removes some legacy features.
File Size and Limits
Both formats share the 2 GB maximum database size limit. However, .accdb handles large databases more efficiently in some scenarios, particularly with the Attachment field type.
New Field Types in .accdb
| Field Type | .mdb | .accdb |
|---|---|---|
| Attachment | Not available | Available — stores files directly in the database |
| Calculated | Not available | Available — stores a calculated result |
| Large Number | Not available | Available — 64-bit integer (bigint) |
| Multi-value fields | Not available | Available (use with caution) |
Removed Features in .accdb
| Feature | .mdb | .accdb |
|---|---|---|
| User-Level Security | Supported | Removed |
| Replication | Supported | Removed |
| Database passwords (simple) | Supported | Replaced with stronger encryption |
Encryption
.mdb files support a simple database password that provides weak protection — it can be bypassed with readily available tools. .accdb files use 128-bit AES encryption when you set a database password, which is genuinely secure.
When to Convert (and When Not To)
Convert if:
- You are the only version of Access in use, or everyone has Access 2007 or later
- You want to use Attachment fields, Calculated fields, or Large Number fields
- You need stronger database encryption
- You want to use data macros
- You are planning to split the database and want the most current format for the back-end
Stay on .mdb if:
- You have users on Access 2003 or earlier who cannot be upgraded
- You use a third-party application that connects to the database via Jet and has not been updated to support ACE
- You rely on database replication (
.accdbdoes not support it) - You have a working User-Level Security setup that you cannot replace right now
Note: Access 365 can open and edit .mdb files. Staying on .mdb is a valid choice — you just cannot use the newer field types or the stronger encryption.
Step-by-Step Conversion
Step 1: Compact and Repair the .mdb First
Before converting, compact and repair the original .mdb file. This removes deleted records, fixes minor corruption, and reduces the file size. Do this in whatever version of Access you currently use:
- Access 2003: Tools → Database Utilities → Compact and Repair Database
- Access 2007+: Database Tools → Compact & Repair Database
Step 2: Make a Backup
Copy the .mdb file to a safe location. You will want the original if anything goes wrong.
Step 3: Open the .mdb in Access 365
Open Access 365. Do not double-click the .mdb file — use File → Open and browse to it. Access will open it in compatibility mode. You will see the version noted in the title bar.
Step 4: Save As .accdb
Go to File → Save As. Under "Save Database As", select Access Database (.accdb). Choose a new filename — do not overwrite the original .mdb. Click Save.
Access will convert the file. The process typically takes a few seconds for small databases and up to a minute or two for larger ones.
Step 5: Compact and Repair the New .accdb
Immediately after conversion, run Compact and Repair on the new .accdb file. The conversion process can leave some overhead that compacting removes.
Step 6: Compile All VBA
Open the VBA editor (Alt+F11) and run Debug → Compile Database. Fix any errors before proceeding. Common issues:
- Missing references: Go to Tools → References and uncheck any marked "MISSING", then find the correct current version
Declarestatement errors: AddPtrSafefor 64-bit Office compatibility (see the section below)- Deprecated methods: Some DAO/ADO methods changed between Jet and ACE
Step 7: Test Thoroughly
Do not assume the conversion worked correctly just because it completed without errors. Test every object:
- Open each table and verify data is intact and row counts match the original
- Run each query and verify results
- Open each form and test all controls and buttons
- Run each report in Print Preview with real data
- Run each macro and verify it completes
- Test all linked tables
What Happens to Specific Features During Conversion
User-Level Security
If the .mdb uses a workgroup file (.mdw) for User-Level Security, Access will warn you during conversion that this security cannot be converted. The database will convert successfully, but all security restrictions will be removed. Anyone who can open the .accdb file will have full access to all data.
You must implement an alternative security model before deploying the converted database. Options:
- Windows file system permissions on the folder containing the database
- A split database with the back-end on a restricted network share
- SQL Server back-end with proper authentication
Database Password
If the .mdb has a simple database password set, you will be prompted to enter it during conversion. The password will be carried over to the .accdb file, but it will now use the stronger AES encryption.
OLE Objects
OLE objects stored in .mdb tables (embedded Word documents, Excel spreadsheets, images stored as OLE) will convert to the .accdb format, but they remain as OLE objects — they do not automatically become Attachment fields. OLE objects in .accdb files still work, but they are less efficient than Attachments and require the source application to be installed to view them.
If you want to migrate OLE objects to the Attachment field type, that is a separate process that requires writing VBA code to extract the binary data and re-import it as attachments.
Replication
If the .mdb was set up for replication (Design Master / Replica), the replication system properties will be removed during conversion. The data will convert, but the replication topology will not. Access 365 does not support replication.
AutoNumber Fields
AutoNumber fields in .mdb files use a 32-bit Long Integer by default. In .accdb, they still default to Long Integer, but you can change them to Large Number (64-bit) if needed. The conversion does not automatically change existing AutoNumber fields.
Fixing 64-bit VBA Issues
If your .mdb contained VBA code with Windows API Declare statements, those will need updating for 64-bit Access 365. The conversion does not fix these automatically.
The pattern is the same for all API declarations:
' Before (32-bit .mdb era)
Declare Function GetSystemMetrics Lib "user32" (ByVal nIndex As Long) As Long
' After (64-bit safe .accdb)
#If VBA7 Then
Declare PtrSafe Function GetSystemMetrics Lib "user32" (ByVal nIndex As Long) As Long
#Else
Declare Function GetSystemMetrics Lib "user32" (ByVal nIndex As Long) As Long
#End If
Note: GetSystemMetrics returns a regular integer (not a pointer), so Long is correct for both versions. Only change Long to LongPtr for values that represent memory addresses, window handles, or other pointer-sized values.
Splitting the Database After Conversion
If your .mdb was a single combined file (tables and interface together), the conversion to .accdb is a good opportunity to split it into a front-end and back-end:
- Back-end: contains only the tables, stored on a network share
- Front-end: contains forms, reports, queries, macros, and VBA, distributed to each user's local machine
Splitting improves performance, makes updates easier (you only replace the front-end), and reduces the risk of corruption from multiple simultaneous users.
To split: Database Tools → Access Database (the "Move Data" group). The wizard will create a back-end file and link the tables automatically.
Verifying the Conversion Was Successful
After conversion and testing, do a final verification:
- Row counts: For each table, compare the record count in the
.accdbto the original.mdb - File size: The
.accdbshould be similar in size to the compacted.mdb(possibly slightly larger due to format overhead) - All objects present: Check that the count of tables, queries, forms, reports, macros, and modules matches between the two files
- Linked tables: Verify all linked tables connect successfully (right-click a linked table → Linked Table Manager → verify)
After the Conversion: New Features to Consider
Now that you are on .accdb, a few features are worth adopting:
Attachment fields: If you currently store file paths as text (pointing to files on a network share), consider whether the Attachment field type would work better for your use case. Attachments store the file inside the database — convenient for portability, but it increases database size.
Calculated fields: Instead of calculated fields in queries, you can now add a Calculated field type directly to a table. Use this sparingly — calculated fields in tables can complicate queries and are not always indexed efficiently.
Stronger encryption: If your database contains sensitive data, set a database password now that you are on .accdb. The AES encryption is genuinely strong. Go to File → Info → Encrypt with Password.
The .mdb to .accdb conversion is one of the most routine maintenance tasks in Access development. Done carefully — with a backup, a compile check, and thorough testing — it is a low-risk operation that opens the door to a decade of improvements in the Access platform.
Work With Access Evolved
If you found this article useful, Access Evolved specializes in exactly this kind of work — from hands-on Microsoft Access support to full database modernization projects.
Need expert help with your Access database? Schedule a free assessment call.
Thinking about migrating?
Ready to move beyond Microsoft Access?
Access is a great starting point, but growing businesses often hit its limits. Anthony Passeri specializes in migrating Access databases to modern platforms — Power Platform, Power Apps, SQL Server, Azure, and more — so you keep your data and workflows without the headaches.
Written by
Anthony Passeri, MBA
Access Expert and Editor
Bridging the gap between Access and the Future
Explore Topics
Keep reading
More on Access Basics
Upgrading from Access 2007 or 2010 to Microsoft 365: Smoother Than You Think
Access 2007 and 2010 already use the .accdb format, so the upgrade to Access 365 is mostly about compatibility settings, VBA tweaks, and taking advantage of features you did not have before.
Upgrading from Access 2003 to Microsoft 365: A Practical Migration Guide
Access 2003 was the last version to use the classic .mdb format and the old menu interface. Upgrading to Access 365 means a new file format, a new UI, and a few features that no longer exist. Here is how to do it right.
Upgrading from Access 97 or Access 2000 to Microsoft 365: What You Need to Know
Still running a database built in Access 97 or 2000? Here is everything you need to know to bring it forward to Access in Microsoft 365 — what works, what breaks, and how to plan the migration.