This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 50%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
I'm having a major issue relinking tables with the latest Current Channel rollout of Version 2212, Build 15928.20216. Trying to programmatically relink tables gives the error 3125-dbo.TableName is not a valid table name.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 77%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
We have the same issue. After applying MS Office update from release 2211 (Build 15831.20098) to 2212 (Build 15928.20002), users no longer able to launch the Access program (accde) with error 3125 "dbo.xxx is not a valid name", even though nothing was changed from programming side.
After dealing with MS Support agent for a week [Case #:34601274], they replied that the issue is out of their support scope and we are suggested to post a question in Microsoft Forum.
Many users experienced the same problem and posted on Microsoft Community as well.
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.
Please advise the root cause and the timetable of fixing the issue in future Office update release. Thank you very much.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 6%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMB%3C/text%3E%3C/svg%3E)
There is a fix to this available with Version 2301 (Build 16026.20146). You may need to manually do an Update Now to get this fix early.
Dear Maria,
Thanks. However, based on the release note, such fix for Access was not mentioned. Would you please confirm?
Hi TC. I just spoke with a Microsoft Access Team member. They are looking into getting the 2301 Current Channel article updated to reflect this fix. He confirmed that it is indeed fixed in 2301. The only evidence I can offer you at this point is this article which still says the status is workaround but promises it will be in 2301 update https://support.microsoft.com/en-gb/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