Your Access Database Lost Support. Your Business Still Runs on It.

The file nobody wants to touch

Many companies have one. A manager built it in Microsoft Access years ago to replace a stack of spreadsheets. It worked. Then more people started using it, more data went in and more of the business came to depend on it. The person who built it may have left. Nobody is quite sure how it works, so nobody changes it. New hires learn which buttons to press and which ones to leave alone, and the file keeps growing on a shared drive in the back office.

That file is often fine for years. The trouble starts when the ground under it moves. This month the ground moved. The last of the older desktop versions of Access are now past end of support, which means the software that opens your file is no longer being fixed. Most people will not notice anything on the day support ends. The file opens the same way it did last week, and that is what makes the problem so easy to put off.

What the evidence says

Microsoft's lifecycle pages list the dates. Access 2016 and Access 2019 reached end of support on October 14, 2025, along with the rest of Office 2016 and Office 2019. Access 2021 and Access LTSC 2021 followed on October 13, 2026. Microsoft also ended support for Office 2013 back in April 2023. If your company bought Office once and kept it for years, rather than paying for a Microsoft 365 subscription, some of your computers may be running one of these versions right now.

Microsoft is clear about what that means. After end of support there are no new security updates, no fixes for other problems and no technical help. The apps may keep working. Microsoft warns that people who keep using them may face serious security risks and that performance and quality can get worse over time.

The file has limits of its own, and those do not change with an upgrade. Microsoft's Access specifications put the maximum size of an Access database at 2 GB, minus the space Access needs for its own system objects. The listed limit is 255 users at once. Microsoft's own guide to moving Access data to SQL Server says plainly that Access and virtual private networks do not get along, which matters for anyone working from home or a second office. Microsoft adds that when a database runs into these limits, it usually points to a design problem.

That same guide lists what SQL Server adds. It can back up a database while people are using it. It can recover after a crash or a power outage in minutes. It works with Windows security, so people sign in with the accounts they already use, and Microsoft calls it the right home for sensitive data like Social Security numbers and card details. Remote staff can keep using the Access screens on their own computer while the data sits safely on a server. Even the free SQL Server Express edition holds up to 10 GB, five times the Access limit.

Why these databases are hard to retire

If the fix were simple, companies would have moved years ago. Most owners know the file is old. What holds them back is fear of breaking something that works, and that fear is reasonable. Three things usually stand in the way.

The logic lives in the forms

An Access file is more than tables. It holds the screens people type into, the reports they print and the macros and code that tie them together. Pricing rules and approval steps often live inside a button on a form. Nobody wrote them down anywhere else, so moving the data means finding the rules first. Some queries also call custom code written inside the file. Microsoft notes that SQL Server cannot run those functions as they are, so someone has to rebuild them on the server.

The tools only move part of it

Microsoft's SQL Server Migration Assistant moves tables and simple queries well. By Microsoft's own description it does not convert forms, reports, macros or VBA code. Tables that use the Attachment field type are not moved, and fields that hold more than one value are not converted. Queries that ask the user for a value are not converted either. Those pieces need a person who reads the file and plans around them. Skip that work and the new system may quietly drop a rule the old one enforced.

Upgrading Office feels like enough

Moving to Microsoft 365 Apps or Office LTSC 2024 brings Access back under support, and Microsoft recommends testing important macros, add ins and complex files before any upgrade. That is the right first step. But a newer copy of Access still opens the same file with the same 2 GB ceiling and the same trouble over a VPN. If the file is already slow, crowded or corrupting now and then, a new Office license will not cure it.

A plan for the Access file you depend on

1. 1List every Access file in use, who uses it and what work stops if it breaks.
2. 2Check which version of Office each person runs and whether it is past end of support.
3. 3Copy each important file and confirm the copy opens before you change anything.
4. 4Test your key forms, reports and macros in a supported version of Access.
5. 5Measure the file size and count the people who use it at the same time.
6. 6For busy or growing files, add primary keys and indexes, then move the tables to SQL Server.
7. 7Keep the Access forms as a front end with linked tables so staff keep the screens they know.
8. 8Write down the business rules you find inside forms and code so they are not lost again.

Not every file needs the full move. A small personal tracker can simply open in a supported version of Access. A shared file that is close to the size limit, slow over a VPN or full of sensitive records is a different story. The files to worry about are the shared ones that hold customer, financial or job data, and the ones where a bad day would stop work. Start there, and leave the rest for later.

What this means if you run a company in Oklahoma

Plenty of Oklahoma businesses grew up on desktop tools. A field services company in Tulsa, a family distributor in Oklahoma City or a county office out west may run core work through an Access file built long ago. Those files were a smart choice when they were made. The question now is whether they still fit how the business works. Often the honest answer is that the data has outgrown the file, even though the screens still suit the people using them.

Staff now log in from trucks, job sites and home offices, and that is exactly where Access struggles. Customer and payment data sitting in a file on a shared drive is also a risk if the software around it is no longer patched. Moving the data to SQL Server while keeping familiar screens is often a modest project. It is much smaller than replacing the whole system, and far cheaper than a lost week of orders. It can also be done in stages, one file at a time, without stopping daily work.

At Oklahoma Data Partners, we help Oklahoma companies find the Access files they depend on, test them on supported software and move the data to SQL Server when it makes sense. If an old database is running part of your business, book a consultation.