Microsoft Access

active

by Microsoft · since 1992 · also known as Access, MS Access, Access Database Engine, ACE, Jet

Desktop database and forms builder bundled with Microsoft 365; still everywhere in back offices.

relationaldatabase engineproprietarylegacy

Overview

Microsoft Access pairs a file-based database engine (ACE, the successor to Jet) with a visual designer for tables, queries, forms, reports and VBA macros. It remains the tool countless analysts and small teams used to build internal apps, and many of those .accdb files are business-critical today. Microsoft has not announced an end of life: Access ships in Microsoft 365 and Office LTSC 2024 (supported to October 2029), but investment is in maintenance mode while new low-code work goes to Power Apps and Dataverse, and the Database Compare tool was retired in 2026. Use it for small, single-site tools, often with tables moved to SQL Server; avoid it for anything multi-user at scale.

Strengths & trade-offs

Strengths

  • +Forms, reports, queries and storage in one tool that business users already have
  • +Very fast to prototype internal CRUD apps
  • +Can link to SQL Server, SharePoint lists and ODBC sources as a front end
  • +Free Runtime lets you distribute apps to users without full licences

Trade-offs

  • −2 GB file limit and file-share locking make corruption and contention common under load
  • −Windows-only; no web or mobile client
  • −Microsoft's low-code focus has moved to Power Platform
  • −VBA-heavy apps are hard to version-control and test

Great for

  • +Small departmental tracking apps
  • +Front ends over SQL Server tables
  • +Ad hoc data cleanup and reporting by analysts
  • +Maintaining existing business-critical .accdb apps

Think twice for

  • −Multi-user apps beyond a handful of concurrent users
  • −Web or mobile access
  • −Data larger than a couple of gigabytes

Capabilities

Native or official first-party support · 6 of 25 tracked

✓Transactions
✓Joins
✓Secondary indexes
✓Triggers
✓Durable persistence
✓Encryption at rest
–Full-text search
–Vector search
–Geospatial
–JSON
–Change data capture
–Stored procedures
–Materialized views
–TTL / expiry
–Pub/Sub
–Columnar storage
–In-memory
–Compression
–Role-based access
–Time travel
–Branching
–Online schema changes
–Streaming ingest
–Offline sync
–Runs in WebAssembly

Scale & consistency

Comfortable data size
Small · ≤ 100 GB
Horizontal scaling
None
Multi-region
No
Transactions
Limited ACID
Consistency
Strong
Schema
Strict
Architecture
Embedded, Single node
Query languages
Access SQL (ACE/Jet SQL), VBA

2 GB per .accdb file and file-share locking limit concurrency; larger apps link to SQL Server tables.

Deployment

Self-hosted Vendor-managed cloud Serverless Embedded Edge Kubernetes operator

Ecosystem

apis & protocolsDAO, ADO, ODBC, OLE DB
client languagesC#, VBA, Python, Java

Alternatives to Microsoft Access

Compare all→
Claris FileMakerRelational31.2

Low-code database app builder for Mac, Windows, iPad and web, owned by Apple's Claris.

microsoft-access vs filemaker →
SQLiteRelational75.5

The in-process SQL engine that ships in every phone, browser and OS: one file, zero servers.

microsoft-access vs sqlite →
Microsoft SQL ServerRelational71.0

Microsoft's flagship RDBMS: T-SQL, columnstore, Always On, and now native vectors and JSON.

microsoft-access vs sql-server →
4DRelational12.8

French integrated database and app-development platform for desktop, client/server and web apps.

microsoft-access vs 4d →
SupabaseRelational54.3

Open-source Postgres backend platform: database, auth, storage, realtime and edge functions in one project.

microsoft-access vs supabase →
FirebirdRelational32.8

Lightweight, MVCC relational database from the InterBase lineage, embeddable or client-server.

microsoft-access vs firebird →

Microsoft Access FAQ

What is Microsoft Access?

Microsoft Access is a relational database by Microsoft, first released in 1992. Microsoft Access pairs a file-based database engine (ACE, the successor to Jet) with a visual designer for tables, queries, forms, reports and VBA macros. It remains the tool countless analysts and small teams used to build internal apps, and many of those .accdb files are business-critical today. Microsoft has not announced an end of life: Access ships in Microsoft 365 and Office LTSC 2024 (supported to October 2029), but investment is in maintenance mode while new low-code work goes to Power Apps and Dataverse, and the Database Compare tool was retired in 2026. Use it for small, single-site tools, often with tables moved to SQL Server; avoid it for anything multi-user at scale.

Is Microsoft Access open source?

No. Microsoft Access is proprietary, closed-source software.

Does Microsoft Access support ACID transactions?

Partly. Microsoft Access offers limited ACID guarantees (for example, single-record or single-partition transactions), with strong consistency.

Does Microsoft Access scale horizontally?

Microsoft Access does not scale horizontally; it runs on a single node, so you scale it up rather than out. It is comfortable at small scale (≤ 100 GB).

How can I run Microsoft Access?

You can self-host it and embed it in your application.

What is Microsoft Access best for?

Microsoft Access is a strong fit for small departmental tracking apps; front ends over SQL Server tables; and ad hoc data cleanup and reporting by analysts. Think twice for multi-user apps beyond a handful of concurrent users.

What are the best alternatives to Microsoft Access?

Common alternatives to Microsoft Access include Claris FileMaker, SQLite, Microsoft SQL Server, 4D and Supabase. The right choice depends on your workload, scale and hosting; WhichDB's smart match ranks them against your requirements.

How popular is Microsoft Access?

Microsoft Access ranks #37 of 844 databases on the WhichDB Score (45.8/100), and #11 among relational databases. The score combines public adoption signals such as package downloads, GitHub activity, job posts and developer discussion.