Access database not working

Is your Access database not working? We can help.

A Microsoft Access triage map showing symptoms, protected files, failure sources, and practical next steps.

When a Microsoft Access database isn't working properly, the problem isn't always obvious. The database may open but forms don't work. A query may suddenly produce an error. Reports may no longer calculate correctly. VBA code may have stopped working. Users may be unable to share the database. The application may have become extremely slow—or it may have stopped working altogether.

Sometimes the problem is a damaged database. Sometimes it is a query, form, report, VBA routine, network configuration, Windows or Microsoft Office issue. And sometimes the application has simply outgrown the way it was originally designed.

Access For Business helps organizations diagnose and solve Microsoft Access database and application problems. You don't need to know what's wrong before you contact us. That's what diagnosis is for.

Get Help With Your Access Database

What “not working” can mean

An Access database can be not working in many different ways.

This broad search usually means the user knows the business system is failing, but not yet whether the cause is the file, code, data, environment, network, users, or application design.

Database won't open

Corruption, file access, permissions, startup logic, or the local Access environment.

Forms won't work

VBA, missing references, form design, underlying query changes, or data-source problems.

Queries fail

SQL changes, table structure, relationships, criteria, data types, or generated VBA SQL.

Reports are wrong

Query logic, calculations, data changes, grouping, filters, or report design.

Database is slow

Queries, indexes, data growth, network use, multi-user setup, or application architecture.

Multiple users have problems

Network behavior, shared-file setup, front-end/back-end deployment, locking, or permissions.

VBA stopped working

Missing references, Office version changes, code errors, ActiveX/COM dependencies, or external apps.

Data won't update

Permissions, update queries, relationships, record locking, linked tables, or validation rules.

Problem appeared after an update

Microsoft Office, Windows, drivers, references, workstation replacement, or changed security settings.

Common situations

Common Microsoft Access problems we solve.

The useful first move is narrowing the symptom and then routing it to the right repair, support, development, performance, or modernization path.

01Startup

The Access database will not open, opens inconsistently, or closes unexpectedly.

02Objects

Forms, reports, queries, macros, or VBA code that used to work now fail.

03Data confidence

Users see different results, missing records, locking behavior, or inconsistent data.

04Linked paths

Linked tables, network paths, permissions, or workstation settings break normal use.

05Performance

The database is slow, unstable, difficult to share, or unreliable for multiple users.

06Continuity

The original developer is unavailable and no one knows where to safely start.

What we ask first

What changed before your Access database stopped working?

One of the most useful questions in Access troubleshooting is simple: what changed? The problem is not always visible in the error message.

Changed signal

A new version of Microsoft Office or Windows was installed.

Changed signal

A computer, server, network path, or file location changed.

Changed signal

A new user, permission setting, report, query, table, or field was added.

Changed signal

VBA code, references, linked tables, or external dependencies changed.

Changed signal

The database began handling substantially more data or more simultaneous users.

First diagnostic questions

Diagnosis starts with the exact symptom and what the business cannot afford to lose.

Symptom

What exactly is not working: opening, searching, saving, reporting, data entry, startup, or a specific workflow?

Trigger

When did it start, and what changed before the issue appeared?

Scope

Does the problem affect one user, several users, or everyone?

Architecture

Is the application split into a front end and back end, and where do those files live?

Business risk

What data, reports, users, deadlines, or business process cannot be disrupted?

From symptom to path

The right help depends on how the Access database is failing.

01ProtectPreserve copies, backups, local front ends, and known-good files before more changes are made.
02LocateFind whether the failure is in the file, startup, object, code, data, user environment, or network path.
03StabilizeChoose repair, troubleshooting, support, performance work, development, or modernization based on evidence.

Choose the closest issue

“Not working” often points to one of these more specific paths.

This page is a triage gateway. The more specific the symptom, the safer and faster the next step can be.

Won't open

If the file will not open or fails during startup, the first concern is preserving copies and determining whether the issue is corruption, startup logic, linked data, permissions, or the user environment.

Learn more

Corrupted or damaged

If Access reports corruption or objects fail after a crash, network interruption, or unexpected shutdown, triage should protect backups before additional repair attempts.

Learn more

Forms, reports, or queries aren't working

If the database opens but key screens, reports, or queries fail, the path to the problem can usually be found by reviewing the object, its data source, and what recently changed.

Learn more

VBA has stopped working

If code or macros fail, the likely causes include missing references, changed Office versions, changed Windows environments, code errors, ActiveX or COM dependencies, and external application dependencies.

Learn more

Slow or unreliable

If the application technically works but has become slow, unstable, or hard to share, performance and multi-user behavior may be the real issue.

Learn more

40+ years of business database experience

Your Access application doesn't have to be replaced.

When an important Access application stops working, the first reaction is often to assume that the entire system needs to be replaced. That's not necessarily the case.

A well-designed Access application can often be repaired, improved, documented, or restructured to continue serving the business. If its data architecture needs to change, the data can potentially move to SQL Server or Azure SQL while the existing Access front end continues to provide the forms, reports, and business processes users already know.

We help you determine the most practical solution rather than jumping to an unproven path.

Microsoft Access Support Access Troubleshooting Database Repair Access Development Access Modernization

Access database problem diagnosis

The objective isn't to guess. It is to identify the cause and the most practical solution.

Database structure

Tables, relationships, queries, indexes, linked tables, and the way the data is organized.

Application

Forms, reports, macros, VBA routines, startup behavior, references, and user workflows.

Environment

Microsoft Access, Office, Windows, workstation settings, network paths, file permissions, and external systems.

Data and users

Data integrity, unusual records, growth, record locking, multi-user operation, and who is affected.

Recent changes

What changed before the problem appeared and whether the practical answer is repair, improvement, support, or modernization.

FAQ

Access database not working questions.

Broad symptoms need a careful first pass. These answers help separate environment issues, repair, troubleshooting, support, development, and modernization.

01Why is my Access database not working?Answer

An Access database may stop working because of corruption, startup errors, broken forms or reports, query changes, VBA errors, linked-table problems, permissions, network issues, workstation differences, or data growth.

02Why is my Microsoft Access database suddenly not working?Answer

A sudden failure often follows a change: Office or Windows updates, a moved database file, a replaced computer, a network change, modified tables or fields, broken references, or code changes. Identifying what changed is one of the fastest ways to narrow the problem.

03Why does my Access database work on one computer but not another?Answer

That often points to the environment rather than the database itself. Differences can include Access or Office versions, missing references, trusted-location settings, permissions, drive mappings, linked-table paths, Windows updates, or local front-end copies.

04What should I do first when an Access database stops working?Answer

Preserve copies and backups, capture the exact error or symptom, identify who is affected, and avoid repeated repair attempts on the only available file until the issue is understood.

05Why are my Access forms, queries, or reports not working?Answer

Forms, queries, and reports can fail because of changed field names, broken joins, invalid criteria, missing references, data-type problems, changed linked tables, or VBA code that builds SQL or controls report behavior.

06Why is my Access VBA not working?Answer

Access VBA problems commonly involve missing references, changed Office versions, changed Windows environments, code errors, ActiveX or COM dependencies, external application dependencies, or security/trust settings.

07Can you support an Access database created by another developer?Answer

Yes. Many support situations involve inherited Microsoft Access applications. The work starts by understanding the forms, reports, queries, VBA, data, linked tables, and business rules before making changes.

08Is an Access database that is not working always corrupted?Answer

No. Corruption is one possibility, but problems can also come from references, startup macros, VBA, permissions, linked tables, network paths, front-end/back-end setup, or changes in the business process.

09Can an unreliable Access database be stabilized?Answer

Often, yes. The practical step may be repair, troubleshooting, better front-end distribution, query work, VBA updates, backup discipline, performance improvements, or planning a stronger data platform.

010When should a not-working Access database be modernized?Answer

Modernization becomes worth discussing when failures keep returning, the application has outgrown its current structure, users need more reliable access, or the business needs capabilities the current Access setup cannot reasonably support.

Begin a discussion

Tell us what is not working in your Access database.

Share the exact symptom, error message, affected users, recent changes, where the files live, and what workflow cannot be disrupted.

Begin a Discussion