Access Error 3125 with linked tables after Office update 2212

Question

Once MS Office is updated to release 2212 (from release 2211 Build 15831.20098 to 2212 Build 15928.20002), we are no longer able to launch the compiled program (accde) with error 3125 'xxx is not a valid name' even though nothing was changed from programming side.

After dealing with Microsoft support for one week [Case #:34601274], the reply was that the issue is out of their support scope (?!) and we are suggested to post a question in Microsoft Forum. Rolling back the release to version 2211 is only an immediate but interim solution and we cannot keep skipping the updates because most of the time, security patches are involved.

Similar issues were found in MS Office update release 2206 (Jul 18, 2022) reported by other Access users on the Internet but Microsoft has fixed it in release 2208 (Sep 13, 2022). The Access program uses linked tables as backend connecting to Azure SQL Server.

Would someone please advise the root cause and the timetable of fixing the issue in future release? Thank you very much.

Answer 1

Microsoft corrected this issue see https://support.microsoft.com/en-us/topic/some-tables-do-not-get-named-with-the-dbo-prefix-when-using-vba-createtabledef-in-access-for-microsoft-365-e31bc63c-b112-452b-9f09-7838eca3ce1f

This issue impacts Access 365, Access 2019 Consumer, and Access 2021 Consumer, Version 2212, Build 15928.20000, and subsequent builds.

STATUS: FIXED

This issue has been fixed in Version 2301 for all impacted Office SKUs.

Answer 2

Hi,

Error 3125 in Microsoft Access typically occurs when there is a problem with the object or element being referenced in your code.

As mentioned by Maria Barnes, Microsoft has fixed this issue.

But in case you still face this issue in future, you can-

1. Make sure that all object names referenced in your code, such as tables, queries, forms, or fields, are spelled correctly and exist in your database. Pay attention to any spaces, special characters, or reserved words in the names.
2. Verify that the data in your tables or queries is accurate and consistent. Data inconsistencies or missing values can sometimes lead to runtime errors.

If these workarounds do not work, you can also have a look at this blog to fix the error 3125 in access database.

Best Regards.