Fixes in Microsoft Access - Version 2610 (Build 16.0.20527.20088)
Known issue in the initial Version 2610 release Some databases may display an incorrect "There isn't enough memory or disk space" message when opening a report or exporting a report to PDF. A correction is planned for the next Version 2610 update. UPDATE: This issue is now fixed in build 16.0.20527.20112. Use 'Update Now' to update to the new build. Zoom Issue Fix Datasheet subforms did not zoom with Ctrl+mouse wheel Using Ctrl+mouse wheel over a subform displayed in Datasheet View now changes its zoom level as expected. Context menus appeared in the wrong location on zoomed forms Right-click menus now open at the selected location regardless of the form's zoom level, including near the lower-right edge of the form. A form divider line could stop halfway across at 50% zoom The divider between form sections now spans the full form width at 50% zoom and other supported zoom levels. Rapid Ctrl+mouse-wheel input could jump from 10% to 1000% zoom Zooming out quickly now stops at the 10% minimum instead of wrapping to the maximum zoom level. Big Forms Issue Fix Horizontal scrolling could snap very wide forms back to the left Design View and Form View can now scroll to controls positioned far to the right without the form unexpectedly returning to its left edge. Text formatting remained limited to 22 inches in wider controls Text can now be formatted and displayed across the full width of fixed-size text controls wider than the former 22-inch form limit. Forms and controls Issue Fix ControlTip text could remain visible after typing began ControlTips now close when keyboard input begins, preventing the tip from covering the form during data entry. Property Sheet text could become unreadable after changing the Office theme The Property Sheet now refreshes both its foreground and background colors immediately after a theme change, without requiring Access to be restarted. Queries and data Issue Fix Bracketed object and control names could occasionally be read incorrectly Access now reliably preserves a name when removing its surrounding brackets. Stability Issue Fix Opening forms with grouped control layouts could cause Access to close unexpectedly Access no longer closes unexpectedly while determining the bounds of grouped layouts when affected forms open in Form View. Changing a subform's SourceObject could cause Access to close unexpectedly Changing a subform's source from VBA during an event now completes without causing Access to close unexpectedly.
Out of memory error - Access Version 2610 (Build 20527.20088)
Multiple customers are reporting out of memory error after Office updated to version 2610 (Build 20527.20088). Some customers would receive the out of memory error after an hour or within a few minutes of use. There are instances where error would not occur, and msaccess would just crash. We are rolling customers back to Office version 2608 (Build 20326.20144), and that seems to resolve this issue. Here is the dump file when crashing occurred. https://www.dropbox.com/scl/fi/zxgjrq1p5tpapmu5uudm8/2610-CRASH-dump-JND.zip?rlkey=72g04gqm7bo3dv20z12vi0uqx&st=0ybz8ixw&dl=0
Unlocking Microsoft 365 Adoption in Engineering, Manufacturing, and Regulated Industries
Executive Feedback to Microsoft Leadership: Expanding the Value of Microsoft 365 Beyond Cloud-First Workflows Executive Summary Microsoft has successfully built the industry's leading cloud collaboration ecosystem around Microsoft 365, OneDrive, and SharePoint. The strategy has delivered substantial value for information workers, distributed teams, and organizations pursuing cloud-first operating models. However, there is a significant and often overlooked customer segment that remains underserved: engineering, manufacturing, healthcare, medical device, industrial, laboratory, defense, and other regulated organizations whose primary workflows are intentionally built around file-based repositories, network shares, PDM/PLM systems, and controlled document environments. The challenge is not opposition to cloud technology. The challenge is that many of these organizations prioritize data integrity, traceability, predictability, and workflow continuity above all else. As a result, they often perceive modern Microsoft productivity capabilities such as AutoSave, coauthoring, and version history as being unnecessarily coupled to OneDrive and SharePoint. This creates an important business opportunity. Microsoft could unlock substantial additional Microsoft 365 adoption and customer goodwill by extending modern document protection and collaboration capabilities to local, network-hosted, and hybrid file environments without requiring a complete migration to OneDrive or SharePoint. This is not a request to replace cloud services. It is a request to recognize that cloud-first and file-based workflows can coexist. The Opportunity Is Larger Than It Appears Many of Microsoft's largest enterprise customers operate in environments where files are not simply documents. They are: Design history files Manufacturing records Engineering drawings Validation reports Device master records Controlled procedures Laboratory data Regulatory submissions Quality records For these organizations, file location, revision control, ownership, auditability, and retention are operational requirements rather than convenience features. Microsoft itself acknowledges that Office AutoSave currently requires files to be stored in OneDrive or SharePoint. Files opened from traditional file-system locations do not receive the same experience. As a result, many organizations feel they must choose between: Maintaining proven operational workflows. Accessing Microsoft's most advanced productivity features. That is a business decision many organizations simply refuse to make. The Real Barrier Is Not Technology. It Is Trust. Discussions around cloud adoption are often framed as a resistance-to-change problem. Research consistently suggests otherwise. Studies examining enterprise cloud adoption repeatedly identify security concerns, data privacy concerns, and control over organizational information as major barriers to adoption. One study found security concerns dramatically increased the likelihood that organizations would reject cloud adoption. Similarly, KPMG's cloud transformation research notes that concerns about data loss, audit findings, compliance issues, and operational risk can slow or limit cloud initiatives. The lesson is important: Organizations rarely reject technology because it is new. They reject technology because they do not trust it with critical business information. Once users experience: unexpected file overwrites, synchronization ambiguity, permission confusion, data residency uncertainty, conflicting document versions, trust declines rapidly. Trust, not functionality, is often the limiting factor. Engineering Users Experience the World Differently Microsoft's cloud ecosystem was largely designed around information-worker collaboration. Engineering organizations frequently operate under different assumptions: Information Worker Priority Engineering Priority Seamless sharing Data integrity Anywhere access Traceability Real-time collaboration Configuration control Ease of use Auditability Cloud accessibility Revision certainty Neither approach is wrong. The challenge is that Microsoft increasingly optimizes for one while under-serving the other. An Example: AutoSave AutoSave is one of the most valuable additions Microsoft has made to Office. The value proposition is obvious: Reduced data loss Improved productivity Lower cognitive burden Better user confidence Microsoft's own documentation describes AutoSave as continuously saving changes while users work, but only when documents reside in OneDrive or SharePoint. From Microsoft's perspective, this design is understandable. From the customer perspective, the message often becomes: "Modern document protection is available, but only if you adopt Microsoft's preferred storage architecture." Many customers view this not as a technical limitation, but as product segmentation. Microsoft Could Learn from Version Control Systems Modern software development solved multi-user document conflicts decades ago. Git was specifically designed around realities such as: multiple devices, multiple contributors, offline work, concurrent editing, conflicting changes. Critically, Git assumes conflicts are inevitable. Rather than hiding them, Git exposes conflicts and provides mechanisms to resolve them. Many engineers trust Git precisely because its behavior is transparent. By comparison, file synchronization systems often attempt to abstract away complexity. When synchronization fails, users can no longer determine: which version is authoritative, which edits are newer, what happened, who changed what. The engineering mindset is frequently: Show me the conflict. rather than Hide the conflict and make a decision on my behalf. The Untapped Hybrid Customer Much discussion around Microsoft 365 assumes organizations are either: Cloud-first, or Legacy. In reality, many enterprises are neither. Many operate as hybrid organizations and intentionally will continue to do so. Research from industry and security organizations continues to show persistent adoption of hybrid and multi-cloud architectures driven by governance, security, compliance, and operational requirements. These customers are not rejecting Microsoft. They are already paying customers. They often purchase: Microsoft 365 Windows Azure Teams Active Directory SQL Server Yet many would immediately purchase additional capabilities if Microsoft offered: Local AutoSave Office AutoSave functionality for: NTFS local storage SMB file shares NAS systems PDM-managed documents Local Version History Built-in document time travel without cloud dependence. Hybrid Collaboration Coauthoring capabilities that operate through enterprise file infrastructure. Enterprise Conflict Resolution Visualization and reconciliation of competing document changes. Network-Aware Document Protection The same confidence users experience in OneDrive without requiring migration to OneDrive. The Revenue Opportunity This is not merely a product-improvement request. It is a business opportunity. A significant portion of engineering and regulated industries remain hesitant to migrate entirely into cloud-centric document ecosystems because the perceived operational risks exceed the perceived benefits. Rather than forcing an all-or-nothing decision, Microsoft could monetize a middle path: Microsoft 365 Hybrid Collaboration A premium offering delivering: AutoSave Version History Recovery Conflict Resolution Audit Visibility for enterprise-controlled file infrastructure. Organizations that decline OneDrive adoption today may still eagerly purchase these capabilities. In effect, Microsoft could create incremental revenue from customers who are already committed to the Microsoft ecosystem but currently feel underserved by a cloud-only feature strategy. Recommendation Microsoft should stop treating file-server and network-share users as transitional users waiting to migrate. Many are not transitioning. Many have intentionally chosen architectures optimized for regulatory compliance, engineering rigor, operational control, and data governance. The future should not require choosing between: modern productivity features, and trusted enterprise workflows. The organizations building medical devices, industrial equipment, aerospace systems, manufacturing infrastructure, energy systems, and critical technologies represent some of Microsoft's most technically sophisticated and commercially valuable customers. They deserve first-class support for the workflows they intentionally operate. The opportunity is not to move every customer to the cloud. The opportunity is to bring Microsoft's best innovations to every customer, regardless of where their files live.
Access 365 Runtime 2605+: MsgBox in Click event stops responding (Zoom related)
Starting with Access 365 Runtime version 2605 (build 20026.20168), MsgBox called within a Click event stops responding under specific conditions. We have confirmed that the issue is related to the Access Zoom feature. Microsoft 365 support advised us to report this issue in the community, so we are posting it here. ■ Affected Versions No issues confirmed prior to May 2026 Version 2605 (build 20026.20168) and later → Affected ■ Reproduction Environment Access 365 Runtime Resolution: 1920×1080 (Full HD), Text size: 100% Issue does NOT reproduce at text size 125% or 150% ■ Sample File We have a minimal sample database (Db1.accdb) that reliably reproduces this issue. It contains two forms (Form A and Form B). We can provide it on request. ■ Steps to Reproduce Open the sample database → Form A opens Click Button A on Form A → Form B opens Click Button B on Form B → MsgBox appears (works as expected) Click “No” in the MsgBox Click the Close button on Form B → Form B closes Click Button A on Form A again → Form B opens Click Button B on Form B → MsgBox should appear, but Access stops responding instead Pressing the Alt key resumes execution and MsgBox appears Note: MsgBox displays correctly the first time Form B is opened (step 3). The issue occurs after Form B has been closed and reopened (step 7). ■ Findings Enabling “Disable zoom” in File → Options → Current Database prevents the issue. This option is available in version 2608 and later. The issue also does not occur if Form A is moved to the far left of the screen, or down to approximately the vertical center of the screen, before performing the steps. ■ Temporary Workaround for Versions 2605–2607 The “Disable zoom” option is not available in these versions. Adding the following code immediately before the MsgBox call avoids the issue: Application.Echo False DoEvents Application.Echo True However, this workaround causes side effects in some forms of our application, such as unexpected termination and unexpected parameter prompts for record sources, so it is not a suitable long-term solution. ■ Request This issue began occurring around May 2026 in an existing application whose code has not been changed. We kindly ask the Access team to investigate and fix this issue so that it does not occur when Zoom is enabled. If anyone else is experiencing the same issue, please let us know. We can share the sample file on request.
New Zoom Feature allways removes like it's never been
Hi everybody, Ever since the zoom feature was introduced, I’ve repeatedly encountered a phenomenon where the feature—despite having been present—suddenly disappears. There is no slider, no zoom option in the ribbon, and no corresponding database options. I am using Microsoft® Access® for Microsoft 365 MSO (Version 2609, Build 16.0.20430.20032, 64-bit) on the Monthly Enterprise Channel. Following an update to this version, the feature reappeared. I opened several databases, and the slider was visible—it worked without any major issues (even though I rarely use it), with no crashes or error messages. Then, upon opening another database, the slider and all other elements related to the zoom feature vanished. When I went back to the previous databases, the feature had disappeared there as well. Restarting the PC and performing a "Quick Repair" had no effect. I have observed the same behavior across the previous five versions; the feature keeps disappearing. It seems that a new "Click-to-Run" update might re-enable it (though I’m not entirely certain). Something—or someone (Microsoft ?)—is disabling it. Fortunately, I haven’t incorporated this new feature into any of my objects or VBA code yet; otherwise, the database would crash! Does anyone have any ideas? Thx 4 readingField disappears when zooming out below 100 Percent with mouse scrolling
Hallo Access-friends, Field disappears when zooming out below 100% with mouse scrolling (See screenshot) Continuous Form. The disappearance of individual fields seems to get worse the faster you scroll through the records with the mouse. If you use the right scrollbar, you don't have this problem or your zoom is 100 and higher. The problem shows up for me when you place a field with a transparent background over a conditionally formatted field. The error is reproducible; I can send a sample database. Another issue (maybe not new): I want a text box not to get focus (Here the big green Textbox ). Normally I do this by setting locked=true, enabled=false. But if the text box has conditional formatting, it can still get focus and then the field will be in foreground whats normal but not wanted. I use this construct for formating Records in contious Forms). The F1 Online description for Textbox-enable doesn’t seem right to me… or am I wrong about that? Hope this helps to make things better. Thanks for reading
Office 2019 for Mac – Perpetual License No Longer Activates
Hello, I purchased a genuine Microsoft Office Home & Business 2019 for Mac perpetual license in 2024. The product was successfully activated and is still registered to my Microsoft account. Until recently, everything worked perfectly. However, Word (version 16.113.2) now refuses to activate and displays a message stating that my Office 2019 license is no longer supported. I understand that Microsoft has ended support for Office 2019, but I purchased a perpetual license, not a subscription, and I would like to continue using the software I paid for. I have already contacted Microsoft Support, and they referred me to this community. Could someone from Microsoft please advise how I can restore my existing license? If this is no longer technically possible, I would appreciate an alternative solution, such as a complimentary upgrade to a compatible Office version. I would prefer not to purchase another license simply because my previously working software can no longer be activated. Thank you for your assistance.
Microsoft Sign In Loop
I am trying to sing into Microsoft 365, but every time I do, it takes me back to the login screen. I sing in with my outlook account, but I can't reach the applications. I can sign in on the browser, but not the applications on my computer. I have tried uninstalling and reinstalling M365, but the issue still persists
