Forum Discussion
Access and SharePoint Integration May Be Broken
I am posting this here in the hopes that a Microsoft MVP or employee may see it, verify the issue, and report it to the right people at Microsoft.
We have a fairly significant LOB application with the front-end hosted in Access and the back-end hosted in SharePoint Online lists. This application has been working well for several years.
Sometime in the past few weeks (last known good date was June 23), a change in either Access or SharePoint (or maybe the Windows OneDrive sync client) seems to have broken integration between the products.
When the modern cache format is enabled (the default), all SharePoint calculated columns unexpectedly show errors, as shown here (in a fresh database where I imported just one list from our site as a test):
Naturally, this completely borks the application, with VB code throwing errors at startup.
Using the legacy cache format, or disabling caching altogether, seems to restore functionality--(though this would come at a cost to performance):
But there is a major caveat to this. Other functionality is apparently broken. We have straightforward update queries, for example, the hang indefinitely in these modes, rendering this an unacceptable work-around.
I have been able to replicate this on several different PCs. Also, on several different SharePoint sites in our tenant.
Currently, this is blocking work for us, and we are hoping to see it resolved as soon as possible. If anyone with knowledge of the right people at Microsoft to call attention to this, we would be grateful for any help.
I am using the Access forum because the last time I tried to get help from SharePoint Online support for an Access-related query issue using SP list data, they had no idea what I was talking about.
(Also, for Access database experts: please do not suggest that we avoid using calculated columns in SharePoint lists. This is a hybrid app with most of our users working with data strictly through SharePoint, and SharePoint views do not support the same features as queries do in Access. Making use of these SharePoint features are essential for these users.)
Our Access version: Microsoft® Access® for Microsoft 365 MSO (Version 2607 Build 16.0.20228.20124) 64-bit
Thank you in advance for any help.
This is now fixed. You will need to restart Access to see the fix.
16 Replies
- Shane Groff
Microsoft
This is now fixed. You will need to restart Access to see the fix.
Thank you, Shane.
Thank you!
Thank you, Shane, for the rapid fix.
Microsoft has released a fix in the Current Channel, Version 2607.
You will need to restart Access to pick up the change(the version/build won't change).
Please clarify for our bug report.
"But there is a major caveat to this. Other functionality is apparently broken. We have straightforward update queries, for example, the hang indefinitely in these modes, rendering this an unacceptable work-around. "
Does this mean that update queries hang indefinitely in BOTH caching modes?
What counts as a "straightforward" update query?I can't replicate this part of the behavior in a list of approximately 30 records. Can you give us a scenario that would illustrate the hanging behavior?
Thanks.
Hi George. I was unable to replicate this secondary issue. It may have been something transient on our end.
To be honest, I did not do much investigation of this other than to note that it was occurring and and thus it would not be a good workaround for us.
I have some other PCs that are still on the problematic build so I will investigate to see if I can create a replication scenario.
We do have some reasonably complicated SharePoint lists with half a dozen or more lookup columns as well as calculated columns, so that might be a factor.
Hi,
Today, we've published George's bug documenting blog post on AccessForever.org. We will keep that post updated until the bug is fixed by Microsoft.
Servus
Karl
****************
Access Forever, News, DevCon
Access-Entwickler-Konferenz AEK
Microsoft has verified this as a regression in Version 2607 (build 16.0.20228.20110), which was released to Current Channel on 2026-07-22.
Reverting to Version 2606 or earlier is a temporary workaround.
We'll get further updates when Microsoft gets the problem fixed.Thanks everyone for the comments and help.
FYI, I rolled back my Office version progressively until I installed build 16.0.20131.20154, and things appear to be working again. This version was released on July 14, 2026. So, it appears that the regression happened after that date.
Thank you to George for the details on how to roll back to a prior release.
Let's hope Microsoft can quickly address this and get things working again on the current release.
The Access team has acknowledged the report of the problem and is investigating.
It's a good idea to temporarily roll back the latest update to see if that restores full functionality for your users.
We'll follow up when we know more.Have this exact same issue. Like for like after a day of testing. Will try the different builds but has stopped all productivity for my Team :- as we can no longer log anything
Microsoft® Access® for Microsoft 365 MSO (Version 2607 Build 16.0.20228.20124) 64-bit
As previously suggested, rolling back the update should allow you to continue working.
I can replicate the error. PubSort is a calculated column.
Microsoft Access (Version 2607) Build 16.0.20228.20124 Current Channel 32-bit
The problem has been reported to Microsoft. It's before hours in Redmond at the time of the report. It will be a while before someone sees it.
In the meantime, try rolling back the update. The links in HeinziAT's post will help.I am neither MVP nor Microsoft employee, but there's one piece of advice which might be helpful to you. According to the build number, you currently use the Current Channel of Office. My recommendation is to try to reproduce the issue with the three Monthly Channel builds (here is a list of the build numbers, here is an instruction on how to change channels, and here is how to install a specific build).
This has the following advantages:
- If this is a blocking issue and it doesn't occur in one of the monthly builds, your users can continue working.
- If it fails even on old builds, you know that the issue is (probably) not Access-side but Sharepoint-side.
- When the bug report reaches Microsoft, knowing when the bug was introduced will help them fix it.
