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.Access announces retirement of Database Compare tool in June 2026
MS Access currently ships a standalone Database Compare tool (DATABASECOMPARE.EXE) that enables comparison of two Access databases. As of June 2026, this tool will no longer be distributed and installed with Office. Access is retiring the Database Compare tool because it depends on components that are no longer available and fails to launch reliably on many Office installs. Because we can no longer provide updated components, it will no longer install with new Office setups. This applies to: Access 2019 volume licensed and Enterprise plans Access 2021, Access 2024, and Microsoft 365 subscriptions Access 2021 and Access 2024 as part of the Office 2021 and Office 2024 perpetual licenses (standalone versions) DatabaseCompare.exe is installed typically under the DCF folder of your Office installation (for example, C:\Program Files\Microsoft Office\Office16\DCF\DATABASECOMPARE.EXE), and it often comes alongside Microsoft Spreadsheet Compare as part of Office Professional Plus or Microsoft 365. In addition, supporting DLLs and configuration files are located within the same DCF subfolder. These files handle database connections, reporting, and comparison functions. These files will be removed. If you're running an older version of Office and have a working version of this tool, you can continue to use it until June 20, 2026. After that, it will be removed and will not be available for download. Therefore, we advise you to find a replacement for Database Compare. You can find similar standalone tools that compare two Access databases from other vendors: AccessDiff: This tool easily compares all objects in Access, including forms, code modules, queries, macros, and more. It is designed to help users retrieve lost software and compare all objects in Access databases. AccdbMerge: This tool is an easy-to-use diff and merge tool for Microsoft Access database files. It compares table definitions, data, forms, modules, and more. A free version is available for the main database objects. DataWeigher: This tool compares and synchronizes data between two MS Access databases. It provides a visual result with each type of record (added, deleted, changed) represented by a different color. The comparison results can be saved as a report or SQL script for data synchronization. Total Access Detective: This tool allows you to find differences between any two objects in one Microsoft Access database, including fields, controls, properties, macro lines, module code, and data. It also supports comparing two blocks of text from text files on disk or the text you copy and paste. We recognize this change may require planning, and we encourage customers to review these alternatives and plan a transition away from Database Compare ahead of its retirement in June 2026.
Access Query Problem
Good afternoon. I have been trying to track down a very strange error that my database has thrown for the first time ever... the query performs a complex math equation based on temperature, chlorine residual and pH time to compute the amount of time required to meet disinfection. This month the temerpature of the water has been historically high and the time required historically low. See the screenshot below. The math is evaluating the time required is greater than the time achieved (which it is not). The query is pasted below. I have recreated the math in excel and cannot duplicate this error. It seems exclusive to Access. When the formula evaluates as 10.0 the results are “YES” if the formula evaluates as 9.9 the result becomes “NO” but should be yes… Any advice would be greatly appreciated. Also, this post keeps getting flagged as SPAM... This is attempt number 5.. Fingers crossed.
Msgbox or Modal window Crash on PC Sleep
This has been an issue for a couple of years, but I haven't spent too much time trying to solve it because I thought it would eventually go away. It hasn't and it is becoming worse as I develop other parts of my application. Situation: When a msgbox (or modal window) is open and the PC sleeps, the application hangs upon PC awake. There's no way to get out it with ending the process. To replicate: Create and save blank database Create one module with a single public test function Enter msgbox "Hang Test", vbOkOnly Hit F5 to run the code. The message box pops up. Leave it. Put PC to sleep manually with windows | power | sleep Awaken PC, Access is now frozen. GPT provides a lot of explanations for this behavior, but it doesn't make sense and must be something that can be addressed. Windows 11, Version 2606 (Build 20131.20126 Click-to-Run)Which SharePoint Communication Site layout has worked best in your organization?
Hi everyone, We're redesigning our SharePoint Online communication site and comparing different homepage layouts for HR, IT, Finance, and Corporate Communications. I'd like to hear from the community: Which homepage layout has worked best in your organization? Which web parts do you consider essential? Have you found any design patterns that significantly improved user adoption? Looking forward to learning from your experiences and recommendations.
A Personal Note to the Access Community
Today is my last day at Microsoft. After many wonderful years, I have accepted Microsoft's Voluntary Retirement Program (VRP) and am beginning a new chapter. It feels a little surreal to write those words. For much of my career, I've had the privilege of working with products, communities, and people I deeply care about. In recent years, that has included serving as Program Manager for Microsoft Access, one of the most passionate, knowledgeable, and dedicated communities in technology. Before I go, there is one message I want to leave you with: Access is alive, well, and continuing to evolve. One of the most common questions I hear is, "Is Access going away?" The answer remains the same as it has always been: No. Access continues to ship with Microsoft 365 and Office, continues to receive engineering investment, continues to receive bug fixes, security updates, accessibility improvements, and yes, new features. In fact, we've released multiple new capabilities recently, including improvements such as enhanced zooming support, larger form and report design capabilities, and new developer-focused functionality, with additional features already in various stages of development and rollout. Over the last few years, I've had the opportunity to work alongside an incredibly talented engineering team that genuinely cares about Access and the customers who depend on it every day. I've seen firsthand the discussions, the prioritization meetings, the customer feedback reviews, the accessibility work, the bug triage sessions, and the long hours spent making sure Access continues to serve businesses, governments, schools, non-profits, and developers around the world. Access remains an important part of Microsoft's productivity ecosystem, and the team remains committed to keeping it relevant, reliable, and useful for years to come. I know many of you closely follow the public roadmap and occasionally worry when it's quiet. What doesn't always make it into public announcements is the steady stream of work happening behind the scenes: security investments, compliance work, accessibility improvements, bug fixes, customer-requested enhancements, and the engineering work required to keep a 30-plus-year-old product healthy in a rapidly changing technology landscape. As for what comes next, I don't yet know who the next Access PM will be or when that transition will occur. What I do know is that Access deserves thoughtful stewardship, active engagement with the community, and a clear understanding of why this product continues to matter. I am hopeful that whoever steps into that role will bring fresh ideas, curiosity, and a commitment to listening to the customers, MVPs, partners, and developers who make this community so special. To our MVPs: thank you for your advocacy, your feedback, and your willingness to tell us what we're doing right and what we're doing wrong. Many of the features we've delivered started as customer requests, conference conversations, forum discussions, and MVP feedback. Your voices matter, and they have made the product better. To the Access developers around the world: thank you for continuing to build solutions that solve real problems. Every time someone says Access is only a relic of the past, I inevitably hear from another organization running a mission-critical application, supporting a small business, managing a research project, tracking inventory, or helping people get work done. The creativity and ingenuity of this community never cease to amaze me. And finally, thank you for letting me be part of your journey. It's been an honor to help tell the story of Access, share new features, write documentation, engage with the community, and occasionally fight to get your favorite feature request prioritized. While I'm retiring from Microsoft, I'll always be rooting for Access and the people who use it. The future of Access belongs to all of you, and I believe that future is bright. Thank you for your support, your passion, and your trust. See you around, Linda Cannon Former Program Manager, Microsoft Access
