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.
If your organisation is still running a database built in Access 97 or Access 2000, you are not alone. Thousands of businesses have mission-critical systems that have been quietly humming along in the .mdb format for two decades. At some point, however, the hardware, the operating system, or the IT department forces the issue. This guide walks you through exactly what to expect when you finally make the jump to Access in Microsoft 365.
Why the Gap Is So Large
Access 97 and Access 2000 predate almost every modern Windows security model. They were designed for Windows 95/98 and early Windows NT environments. The jump to Microsoft 365 Access (which is essentially Access 2019/2021 under the hood) spans roughly 25 years of development. That means:
- The file format changed completely (
.mdb→.accdb) - The security model was rebuilt from scratch
- The VBA engine was updated multiple times
- Several features were removed or replaced
- 64-bit Office introduced new compatibility requirements
The good news: the core database engine, query language, and form/report designer are still recognisable. Most of the logic in your old database will survive the move.
Step 1: Audit Your Existing Database Before Touching Anything
Before you open the old .mdb in a newer version of Access, do a full audit:
Document everything:
- List all tables, queries, forms, reports, macros, and modules
- Note any linked tables (especially to other
.mdbfiles or ODBC sources) - Record any ActiveX controls used on forms
- Check for any references to external libraries in the VBA editor (Tools → References)
Make a backup:
Copy the .mdb file to a safe location. Do not work on the original.
Check for corruption first: Run the Compact and Repair utility on the original file in whatever version of Access you currently have. Fix any corruption before attempting an upgrade.
Step 2: Understand What Will Break
Features Removed in Access 2007+ (and therefore gone in 365)
| Feature | Status in Access 365 | Alternative |
|---|---|---|
User-Level Security (workgroup files, .mdw) | Removed | Windows authentication or split database with file permissions |
Data Access Pages (.htm web pages) | Removed | Power Apps or SharePoint |
| Replication | Removed | SharePoint sync or SQL Server replication |
| Pivot Table / Pivot Chart views on forms | Removed | Power BI or Excel pivot tables |
Access Snapshots (.snp) | Removed | Export to PDF |
| OLE objects stored directly in tables | Still works but problematic | File path references (see our OLE vs File Paths guide) |
User-Level Security — The Biggest Headache
If your Access 97/2000 database uses a workgroup information file (.mdw) to control who can open tables, run queries, or access forms, that security model is completely gone in Access 365. There is no migration path — you must redesign security from scratch.
Your options:
- Split the database — keep the back-end data file on a server share with Windows NTFS permissions controlling who can read/write the folder
- Migrate to SQL Server — use SQL Server logins and roles for proper multi-user security
- Use Access with a login form — a VBA-based login form that controls which forms users can open (security through obscurity, not recommended for sensitive data)
VBA Changes
Access 97 and 2000 used VBA 5/6. Access 365 uses VBA 7 on 64-bit Office. Key issues:
Declare statements for Windows API calls must be updated:
' Old (Access 97/2000 — 32-bit only)
Declare Function GetTickCount Lib "kernel32" () As Long
' New (Access 365 — works on both 32-bit and 64-bit)
#If VBA7 Then
Declare PtrSafe Function GetTickCount Lib "kernel32" () As LongPtr
#Else
Declare Function GetTickCount Lib "kernel32" () As Long
#End If
Any module that calls Windows API functions directly will need this treatment. The VBA editor in Access 365 will flag these with a compile error when you first open the database.
Long vs LongPtr:
Pointer-sized values (window handles, memory addresses) that were stored as Long in 32-bit Access must become LongPtr in 64-bit Access 365.
Removed or changed object model members: Some DAO and ADO properties changed between versions. Run a full compile (Debug → Compile) immediately after conversion and work through every error.
ActiveX Controls
If your forms use third-party ActiveX controls (calendar pickers, grid controls, progress bars), those controls must be:
- Available as 64-bit versions (most old ones are not)
- Registered on every machine that runs the database
Many popular Access 97-era ActiveX controls are simply no longer available. You will need to replace them with native Access controls or find modern equivalents.
The built-in Calendar control that shipped with Access 97/2000 was removed in Access 2007. Replace it with the Date Picker available in Access 365 forms.
Step 3: Convert the File Format
Once you have audited the database and understand what needs fixing, the conversion itself is straightforward.
In Access 365:
- Open Access 365 (do not open the
.mdbfile yet) - Go to File → Open and browse to your
.mdbfile - Access will open it in compatibility mode
- Go to File → Save As → Access Database (
.accdb) - Choose a new filename and location — do not overwrite the original
- Click Save
Access will convert the file. This process:
- Converts all tables, queries, forms, reports, macros, and modules
- Does not fix broken VBA or missing references
- Does not recreate User-Level Security (it is simply stripped out)
After conversion, immediately run Database Tools → Compact and Repair on the new .accdb file.
Step 4: Fix Compile Errors
Open the VBA editor (Alt+F11) and run Debug → Compile Database. Work through every error:
- Missing references — go to Tools → References and uncheck any marked as "MISSING". Find the correct modern equivalent.
Declarestatement errors — addPtrSafeand update data types as shown above- Removed object model members — look up the modern equivalent in the Access VBA documentation
Do not proceed until the database compiles cleanly.
Step 5: Test Every Form, Report, and Query
Systematic testing is essential. Create a checklist of every object in the database and test each one:
- Forms: open each form, test all buttons and controls, verify data loads correctly
- Reports: run each report with real data, check formatting and calculations
- Queries: run each query and verify results match the original
- Macros: run each macro and verify it completes without errors
- Linked tables: verify all linked tables still connect correctly
Pay special attention to:
- Any form that used the old Calendar ActiveX control
- Any report that used Snapshot export
- Any query that relied on User-Level Security permissions
Step 6: Address the Trust Center
Access 365 has a Trust Center that controls whether macros and VBA run. When users open your converted database on a new machine, they may see a security warning bar.
Solutions:
- Add the database folder to the list of Trusted Locations (File → Options → Trust Center → Trust Center Settings → Trusted Locations)
- Compile the database to an
.accdefile for distribution (this locks the VBA but removes the warning) - Use a digital certificate to sign the VBA project
Performance Considerations
Access 97/2000 databases that were "fast enough" on old hardware may feel sluggish on modern machines — not because modern hardware is slower, but because:
- The
.accdbformat has more overhead than.mdbin some scenarios - 64-bit Office has different memory characteristics
- Old queries written without indexes may have been fast on small datasets that have since grown
After conversion, run the Performance Analyzer (Database Tools → Analyze → Analyze Performance) and review its suggestions.
When to Consider Going Further
If your Access 97/2000 database has more than a handful of users, stores sensitive data, or is genuinely business-critical, the conversion to .accdb is a good opportunity to ask whether Access is still the right tool.
Consider:
- SQL Server back-end — if you have more than 5–10 simultaneous users or data integrity is critical
- Power Apps + Dataverse — if you need web or mobile access
- Access + SharePoint — if your organisation is already on Microsoft 365 and needs basic multi-user access
The upgrade from Access 97/2000 to Access 365 is very achievable for most databases. The key is patience, thorough testing, and not skipping the audit phase.
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.
Still running Access 97 or 2000? Schedule a free call and get an honest assessment of your modernization options.
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 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 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.
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.