It seems every few months another article pops up declaring that Access is obsolete, on its way out, or being quietly replaced. Then I have to, once again, set the record straight. These are generally written by people who either don't fully understand Access, have an axe to grind, don't consider Access a "real" database solution, or are trying to sell non-Access solutions and are trying to paint it in a negative light. It's getting old, folks. (1)

The headlines change, but the arguments are always the same. File size limits. Corruption. Security. Cloud. Mobile. It becomes a kind of echo chamber where the same talking points get repeated without much technical context. Rather than dismissing those claims outright, it's worth walking through them one by one and separating legitimate considerations from misunderstandings about how Access is actually used in the real world.

One of the most common arguments centers around the 2GB file size limit. On paper, that sounds restrictive, and technically it is true that an individual ACCDB file cannot exceed 2GB. But framing that as the practical limit of an Access solution misunderstands how Access is deployed. Access is not just a file, it is a development platform. In production environments, databases are routinely split so that the front end contains forms, reports, queries, and code while the back end stores only the data tables. Once the data is separated, you are no longer confined to a single file. You can link multiple back-end databases or move the data entirely to SQL Server, including the free SQL Express edition. Many organizations run Access front ends against enterprise-grade database servers with millions or even billions of records. At that point, the 2GB limit becomes largely irrelevant. Presenting it as a hard scalability ceiling is like judging a truck's hauling capacity based on the size of its glove compartment.

Another familiar criticism is that multi-user Access databases are prone to corruption. There is a kernel of truth here, but context matters. If multiple users open the same unsplit ACCDB file over a network share, particularly over unstable Wi-Fi, corruption risk does increase. However, that deployment model has been considered poor practice for decades. Proper multi-user architecture uses a local front end installed on each workstation connected to a shared back end on a server, or better yet, a SQL Server data store. Under that model, corruption is uncommon and typically recoverable using built-in repair tools. Modern Access includes record locking, transaction handling, and compact-and-repair utilities designed specifically to manage multi-user environments. Blaming Access for corruption in badly deployed systems is less a product flaw and more a design and infrastructure issue.

The Windows-only argument is another point often raised as evidence that Access is obsolete. It is true that Access is a Windows desktop application without a native browser or mobile version. But whether that is a limitation depends entirely on the environment. Many businesses already operate in Windows-centric ecosystems where employees spend their entire workday on Windows desktops. In those contexts, Access being Windows-only is not a barrier. And when web or mobile access is required, Access does not have to stand alone. It can serve as one interface layered over shared data that is also exposed through web applications, remote desktops, or Power Apps overlays. The lack of a browser-native version does not prevent Access from participating in broader, hybrid solutions.

Security is another area where Access is frequently criticized, particularly around the absence of native row-level security. This critique assumes Access is meant to function as the primary security boundary, which is rarely the case in serious deployments. Security is typically enforced at the data layer using SQL Server permissions, Active Directory integration, and server-level role controls. When Access is used as a front end to a secured back end, the system inherits the security model of that database server. Evaluating Access as if it must independently satisfy enterprise regulatory frameworks like GDPR or CCPA misunderstands its architectural role within a multi-tier system.

A related claim is that Access databases tend to live in scattered folders, invisible to IT governance and backup processes. That scenario certainly happens, but it is not unique to Access. Excel files, shadow SaaS accounts, unmanaged SharePoint sites, and local data silos exist in every technology environment. Governance is an organizational discipline, not a software feature. Well-managed companies standardize storage locations, enforce backup policies, and control deployments regardless of the platform involved. Access databases can be centrally managed just as effectively as any other business application.

Some critics also frame VBA and macros as a liability, arguing that Access systems become dependent on the individual who built them. If that person leaves, the system becomes difficult to maintain. While that risk exists, it is not unique to Access. Custom code dependencies arise in every development platform, from .NET applications to Python automation scripts. The solution lies in documentation, version control, and development standards. Access's ability to empower domain experts to build solutions rapidly is one of its greatest strengths, not an inherent weakness.

Much of the modern narrative positions the Microsoft Power Platform as the successor to Access. There is no doubt Microsoft is investing heavily in Power Apps, Dataverse, and cloud-based development tools. But investment does not equal replacement. The two platforms serve overlapping yet distinct purposes. Access excels at rapid desktop application development, complex form design, and offline or local-network solutions. Power Apps focuses on browser and mobile deployment with deep cloud integration. Even Microsoft messaging tends to frame them as complementary tools within a broader ecosystem. It is also worth noting that Power Platform introduces subscription licensing and operational costs that many small and mid-sized businesses are reluctant to take on when a desktop solution already meets their needs.

Comparisons to SaaS tools like Airtable and Notion often appear in these discussions as well. These platforms offer impressive collaborative interfaces and lightweight relational capabilities. However, equating them with Access for full-scale application development stretches the comparison. Access supports complex relational schemas, advanced query logic, transactional processing, VBA automation, and deep reporting capabilities. Airtable and Notion prioritize usability and collaboration over relational depth and enterprise integration. They are excellent tools, but they are not direct replacements for mature Access applications.

Perhaps the most dismissive claim is that Access is now useful only for prototyping or small offline teams. That characterization overlooks more than three decades of production deployments across industries including healthcare, manufacturing, education, logistics, and government. Access continues to serve as a primary business system for many organizations and as a front end to enterprise databases for others. Its rapid development speed, low deployment cost, and tight integration with the Microsoft Office ecosystem make it uniquely efficient for a wide range of internal business solutions.

None of this is to suggest Access is the right tool for every scenario. If an organization requires massive cloud-scale concurrency, public-facing web platforms, or mobile-first architecture, other technologies are better suited. The broader software landscape has evolved, and cloud-native systems are increasingly common. But those trends expand the available toolbox rather than rendering existing tools obsolete.

It is also worth recognizing that many "Access is dying" narratives originate from companies selling migration services, cloud platforms, or consulting engagements. That does not invalidate every technical concern they raise, but it does influence how the story is framed. There is a difference between objective analysis and marketing-driven urgency.

Microsoft Access is not dead.

It is not being discontinued.

It remains a supported, actively maintained desktop database platform that fills a specific and valuable role. For the right projects, it is still one of the fastest ways to transform a business need into a working solution. The industry may be evolving, but evolution does not automatically mean extinction.

Richard Rost
Access Learning Zone
5-Time Microsoft MVP
Access developer with over 30 years experience

(1) I normally don't link to these types of articles, but I'm hoping some of you will visit that site and pile on in the comments. :)