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.

A
Anthony Passeri, MBA
••9 min read
Upgrading from Access 2007 or 2010 to Microsoft 365: Smoother Than You Think

If your database was built in Access 2007 or Access 2010, you are already most of the way to Access 365 compatibility. Both versions use the .accdb file format, the Ribbon interface, and the ACE database engine — the same foundations that Access 365 is built on. There is no file format conversion required.

That said, "mostly compatible" is not the same as "just works." This guide covers the specific issues that catch Access 2007/2010 databases out when they move to Access 365, and the new features worth adopting once you are there.

What You Do Not Need to Worry About

Compared to upgrading from Access 97 or 2003, the 2007/2010 → 365 path skips several major headaches:

  • No file format conversion — .accdb files open directly in Access 365
  • No User-Level Security migration — that was already removed in Access 2007
  • No Ribbon learning curve — the interface is the same (with minor additions)
  • No Data Access Pages — already gone before 2007
  • No Pivot Table/Chart views on forms — removed in Access 2013, but most 2007/2010 databases do not rely on them heavily

The Main Issue: 32-bit vs 64-bit Office

The most common problem when moving from Access 2007/2010 to Access 365 is the switch from 32-bit to 64-bit Office. Microsoft 365 installs as 64-bit by default on modern Windows systems.

If your VBA code contains any Declare statements for Windows API functions, they will fail with a compile error on 64-bit Access 365.

How to Check

Open the VBA editor (Alt+F11) and run Debug → Compile Database. If you see errors like:

The code in this project must be updated for use on 64-bit systems.

or

Compile error: The declaration of the function 'X' in the current module is incompatible with the declaration of the function 'X' in module 'Y'.

You have 64-bit compatibility issues to fix.

How to Fix Them

Add PtrSafe to every Declare statement and update pointer-sized return values from Long to LongPtr:

' Access 2007/2010 (32-bit)
Declare Function ShellExecute Lib "shell32.dll" Alias "ShellExecuteA" ( _
    ByVal hwnd As Long, _
    ByVal lpOperation As String, _
    ByVal lpFile As String, _
    ByVal lpParameters As String, _
    ByVal lpDirectory As String, _
    ByVal nShowCmd As Long) As Long

' Access 365 compatible (32-bit and 64-bit)
#If VBA7 Then
    Declare PtrSafe Function ShellExecute Lib "shell32.dll" Alias "ShellExecuteA" ( _
        ByVal hwnd As LongPtr, _
        ByVal lpOperation As String, _
        ByVal lpFile As String, _
        ByVal lpParameters As String, _
        ByVal lpDirectory As String, _
        ByVal nShowCmd As Long) As LongPtr
#Else
    Declare Function ShellExecute Lib "shell32.dll" Alias "ShellExecuteA" ( _
        ByVal hwnd As Long, _
        ByVal lpOperation As String, _
        ByVal lpFile As String, _
        ByVal lpParameters As String, _
        ByVal lpDirectory As String, _
        ByVal nShowCmd As Long) As Long
#End If

The #If VBA7 Then conditional compilation block means the same code works on both 32-bit and 64-bit Office — useful if you have a mixed environment.

Fields that need LongPtr instead of Long:

  • Window handles (hwnd, hWnd)
  • Memory addresses and pointers
  • Return values from API functions that return handles

Fields that stay as Long:

  • Regular integer values (counts, flags, error codes)
  • Values that are not pointer-sized

Common Windows API Calls in Access Databases

Here are the most frequently used API declarations in Access 2007/2010 databases and their 64-bit-safe versions:

Open a file or URL with the default application:

#If VBA7 Then
    Declare PtrSafe Function ShellExecute Lib "shell32.dll" Alias "ShellExecuteA" ( _
        ByVal hwnd As LongPtr, ByVal lpOperation As String, _
        ByVal lpFile As String, ByVal lpParameters As String, _
        ByVal lpDirectory As String, ByVal nShowCmd As Long) As LongPtr
#Else
    Declare Function ShellExecute Lib "shell32.dll" Alias "ShellExecuteA" ( _
        ByVal hwnd As Long, ByVal lpOperation As String, _
        ByVal lpFile As String, ByVal lpParameters As String, _
        ByVal lpDirectory As String, ByVal nShowCmd As Long) As Long
#End If

Get the Access application window handle:

#If VBA7 Then
    Declare PtrSafe Function FindWindow Lib "user32" Alias "FindWindowA" ( _
        ByVal lpClassName As String, ByVal lpWindowName As String) As LongPtr
#Else
    Declare Function FindWindow Lib "user32" Alias "FindWindowA" ( _
        ByVal lpClassName As String, ByVal lpWindowName As String) As Long
#End If

ActiveX Controls

Access 2007/2010 databases sometimes use third-party ActiveX controls that were compiled as 32-bit only. These will not load in 64-bit Access 365.

How to identify the problem: Open a form that uses an ActiveX control. If you see an empty box with a red X or an error message about the control not being registered, the control is either missing or 32-bit only.

Solutions:

  1. Find a 64-bit version of the same control from the vendor
  2. Replace the control with a native Access 365 equivalent
  3. If your organisation must use 32-bit Office, install the 32-bit version of Microsoft 365 instead (this is a valid option — 32-bit Office runs fine on 64-bit Windows)

Features Removed Between Access 2010 and Access 365

Pivot Table and Pivot Chart Views (Removed in Access 2013)

If your Access 2010 database uses Pivot Table or Pivot Chart views on forms, those views are gone in Access 365. The form will still open in Form view and Datasheet view, but the Pivot options will not appear.

Alternative: Export the data to Excel for pivot analysis, or build a Power BI report connected to your Access database.

Web Databases / Access Web Apps (Removed in Access 2018)

Access 2010 introduced "Web Databases" that could be published to SharePoint. Access 2013 extended this with "Access Web Apps" hosted in SharePoint Online. Both features were discontinued. If your database was designed as a Web Database, the web-facing components will not work — only the local desktop portion will open.

Trust Center and Macro Security

Access 365 has the same Trust Center as Access 2010, but default security settings may differ depending on your organisation's Microsoft 365 configuration. If users see a yellow security warning bar when opening the database:

  1. Add a Trusted Location: File → Options → Trust Center → Trust Center Settings → Trusted Locations → Add new location. Add the folder where the database lives.

  2. Use a network path, not a mapped drive: Trusted Locations work more reliably with UNC paths (\\server\share\folder) than with mapped drive letters (Z:\folder).

  3. Compile to .accde: Database Tools → Make ACCDE creates a compiled version with locked VBA. Users cannot modify the design, and the security warning is reduced.

What Is New in Access 365 That You Should Use

Once your database is running cleanly, these Access 365 features are worth adopting:

Tell Me / Search Bar

The search bar at the top of the Ribbon (type what you want to do) is a fast way to find commands without navigating the Ribbon. Useful for less-frequent tasks.

Improved Date Picker

The date picker control on forms is more reliable in Access 365 than in 2007/2010. If you built a custom date picker using a calendar ActiveX control, consider replacing it with the built-in date picker.

Large Number Field Type

Access 365 added a Large Number field type (equivalent to SQL Server's bigint) that stores integers up to 9,223,372,036,854,775,807. If any of your tables store large numeric IDs or financial figures that approach the Long Integer limit (2,147,483,647), consider switching those fields to Large Number.

Linked Table Manager Improvements

The Linked Table Manager in Access 365 is significantly improved over the 2007/2010 version. It can refresh all linked table connections at once and shows the current connection status for each linked table. If your database uses linked tables to a back-end .accdb or SQL Server, the new manager makes maintenance much easier.

Dark Mode Awareness

Access 365 respects the Windows dark mode setting. Forms and reports will not automatically switch to dark mode (your custom colour choices remain), but the Access chrome (title bar, Ribbon, Navigation Pane) will follow the system theme.

Performance: Is Access 365 Faster?

For most databases, Access 365 on modern hardware is noticeably faster than Access 2007/2010 on the hardware those versions originally ran on. However, if you are comparing Access 365 to Access 2010 on the same modern machine, performance is similar.

A few things that can make Access 365 feel slower than expected:

  • OneDrive sync: Never store an Access database in a OneDrive-synced folder. The continuous file sync conflicts with Access's file locking and causes corruption and slowness. Store databases on a local drive or a traditional network share.
  • Antivirus scanning: Real-time antivirus scanning of .accdb files can significantly slow down Access. Add the database folder to your antivirus exclusion list.
  • Large unindexed tables: If your tables have grown substantially since 2010, add indexes to fields used in query criteria and joins.

Summary: Your Upgrade Checklist

  • Back up the .accdb file before making any changes
  • Open in Access 365 and run Debug → Compile Database
  • Fix all Declare statements for 64-bit compatibility
  • Check all forms for missing or broken ActiveX controls
  • Test every form, report, and query with real data
  • Set up Trusted Locations on all user machines
  • Move the database off OneDrive if it is currently synced there
  • Consider compiling to .accde for distribution

The Access 2007/2010 to 365 upgrade is the most straightforward of all the Access version migrations. For most databases, the only real work is fixing Declare statements — and many databases do not have any at all.

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.

Upgrading from Access 2007 or 2010 and thinking about what comes next? Schedule a free call and get a modernization roadmap.

Schedule a Free 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.

A

Written by

Anthony Passeri, MBA

Access Expert and Editor

Bridging the gap between Access and the Future

Explore Topics

#upgrade#migration#access 2007#access 2010#microsoft 365#accdb#64-bit

Keep reading

More on Access Basics