A family of Microsoft relational database management systems designed for ease of use.
Hi Wayne,
Thank you for sharing the details of your situation.
Since the same split database works correctly on other computers, including one running a newer build, the issue may be specific to the affected Access installation, the local front-end copy, or Build 20430.20118.
Before making any changes, back up both the front-end and back-end database files. Here are some steps you can try
- Replace the local front-end with a fresh copy from a computer where the database is working correctly. If necessary, relink the tables to the back-end database.
- Make sure no other users have the database open, then go to File > Info > Compact & Repair Database.
- Press Alt + F11, go to Tools > References, and check whether any references are marked MISSING. Then select Debug > Compile to check for VBA errors.
- Start Access in Safe Mode by pressing Windows + R, entering the following command, and then testing the database again:
msaccess /safe
- If the error does not occur in Safe Mode, disable any nonessential add-ins under File > Options > Add-ins, restart Access, and test again. You can also hold Shift while opening the database to bypass startup actions and check whether an AutoExec macro or startup form is causing the issue.
- Reference: Bypass startup options when you open a database
- Go to File > Account > Update Options > Update Now to install the latest available Office build. Since you mentioned that the problem does not occur on Build 20430.20140, updating may help determine whether the behavior is limited to Build 20430.20118.
- If the issue continues, go to Windows Settings > Apps > Installed apps > Microsoft 365 > Modify. Run a Quick Repair first, followed by an Online Repair if necessary.
If the issue persists after completing these steps, report it directly to Microsoft from Access by going to Help > Feedback > Report a problem. Include the exact error message, the affected Access build, whether you are using 32-bit or 64-bit Access, screenshots, and the steps that consistently reproduce the issue. This information will help the Microsoft product team investigate whether the behavior is related to Build 20430.20118.
I hope this information helps move the case forward. Should you have any further questions or need additional assistance, please feel free to share them in the comment below. I'm very happy to help.
If the answer is helpful, please click 'Yes' and kindly upvote it.
Note: Follow the steps in the forum documentation to enable email notifications if you want to receive email notifications related to this topic.