Others

Fix Microsoft Access Buttons Not Working After Moving a Database

Natalie TaylorNatalie Taylor Nov 20, 2026 868 views

Question details

Restore command buttons that no longer open forms after a split Access database is moved to one computer.

Fix Access Buttons Not Working After Moving a Database
Product
Microsoft Access 2016 through Microsoft 365
Device & OS
not provided
Scenario
The front end and back end were moved to the same computer, and the back-end tables were relinked.
Observed behavior
The main form displays data, but clicking a command button that should open another form produces no response.
Before you start

Confirm that you are opening the front-end database containing the forms and that its linked tables display data. Note the name of a button and the form it should open so you can test the correct event.

Solution 1Recommended

Check the Button Event and Compile the Access VBA Project

Use this method to find missing event procedures, compile errors, or code that stops before opening the target form.

Moving a split database to one computer does not require a conversion from multi-user to single-user use. Working linked tables do not necessarily mean the button code is running.

1
Inspect the button event

Right-click the main form in the Navigation Pane and select Design View. Select the affected button, open Property Sheet, and check On Click on the Event tab.

2
Open the event procedure

If On Click is set to [Event Procedure], click the build button (...) beside it to open the VBA procedure. Confirm that the procedure exists and contains the action intended to open the target form.

3
Compile the project

In the VBA editor, select Debug > Compile. Correct any errors Access reports, then compile again.

4
Test with a breakpoint

Click a line near the start of the button procedure and press F9 to set a breakpoint. Return to Form View and click the button; if the breakpoint is reached, use F8 to step through the code and identify where it stops.

5
Check the event assignment

If the breakpoint is not reached, return to the button's Property Sheet > Event tab and verify that On Click points to the intended event procedure or macro.

Check the Button Event and Compile the Access VBA Project
Free Microsoft Office alternative

Use WPS Office for Documents and Spreadsheets

WPS Office is a free, lightweight alternative for everyday Office files, with a familiar interface and format compatibility that helps you move existing work. It does not repair Access databases or run Access forms and VBA.

Work with Microsoft Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTXUse a familiar interface for common document and spreadsheet tasksOpen existing Office files to ease migrationKeep using Microsoft Access for database forms and command buttons
QA img-9

Frequently Asked Questions

Does a split Access database need to be converted for one user?

No. The front end and back end can both be on one computer without a special conversion. Relink the tables if their paths have changed, then check the button events and VBA code.

Why does the form show data when its buttons do nothing?

Linked tables may be working even if button events are missing, VBA has errors, or Access has blocked active content. Check the button's On Click property and compile the project from the VBA editor's Debug menu.

What if the button's On Click property contains a macro?

In the form's Design View, select the button and open Property Sheet > Event. Use the build button (...) beside On Click to inspect the assigned macro and verify that its action opens the intended form.

Will opening the database exclusively fix the buttons?

Not necessarily. Exclusive mode controls access by other users; it does not repair missing event procedures or blocked code. Use it only if necessary, such as when an administrative operation requires exclusive access.