VBA problem in Office 2024

Question

Refer to my previous posts, a group of users claimed that their VBA in Excel fail after updated the Microsoft Office 2024 Version 2408 (Build 17932.20602) (Nov 2025) to Version 2408 (Build 17932.20620) (Dec 2025). They claimed this is bug of patch update and will be resumed by coming patch / version.

 

As of today, they tested the Version 2408 (Build 17932.20638) (Jan 2026) & Version 2408 (Build 17932.20670) (Feb 2026) still fail of their VBA.

 

The work around is fail back to Version 2408 (Build 17932.20602) (Nov 2025) and stop the version update.

 

Since users rejected to provide the source code, we just know that the major function is using VBA to connect the database in another device.

 

My objective is updating the Microsoft Office version to meet the security requirement. Therefore, may I have an information about:

 

1.      Is it the bug / known issue of the VBA issue since the version Dec 2025? If yes, any further workaround or solution?

2.      If it is not bug / known issue, is it caused by the update objective? (i.e. security level upgraded for connection or VBA code updated)

3.      If the point 2 is Yes, what should users can do?

Thanks

 

https://learn.microsoft.com/en-us/answers/questions/5685877/problem-of-office-2024

https://learn.microsoft.com/en-us/answers/questions/5685876/excel-problem-after-updated-office-2024

 Capture.PNG

Answer 1

Dear @Ka Ho Cheng,

Thank you for posting your question in the Microsoft Q&A forum.

I understand the frustration this persistent VBA issue is causing, especially since reverting to an older build is the only current workaround. Based on the error in your image ("Unable to clear table Archive Index from temporary database") and the timeline of the updates, here is my assessment of the situation:

1. Is this a known problem since the December 2025 update?
   • Currently, there is no official "known problem" publicly documented in the Microsoft 365 release notes for Build 17932.20620 regarding general VBA database connectivity. However, the consistent failure starting from that specific patch suggests a regression or a change in how Excel handles external database connections or temporary files.
2.  Is this caused by security or architectural changes?
   • It is very likely that the December and subsequent updates included security hardening for remote connections or macro execution.
   • Microsoft has been actively tightening security for VBA macros that access network locations or use legacy database drivers (like Jet or older ACE OLEDB providers).
   • Credential/Protocol Changes: If the VBA code connects to another device, the update may have blocked a legacy authentication protocol or an unencrypted connection that was previously allowed.
   Recommended actions for users Since the users cannot share the source code, I recommend they try the following:
   • Check Trust Center Settings: Ensure that the "Trusted Locations" include the network path of the database and that "Enable all Data Connections" is checked under File > Options > Trust Center > Trust Center Settings > External Content.
   • Update Connection Strings: Ensure the VBA code is using the latest Microsoft Access Database Engine drivers (ACE) rather than legacy ones.
   • Review Temporary Permissions: The error "Unable to clear table... from temporary database" suggests a permission issue in the Windows Temp folder or the folder where the database reside. Ensure the user has Full Control over the database destination.

Because this issue persists across multiple builds and appears to be tied to internal product changes or security policies, I strongly recommend that your IT Admin raise a formal support ticket via the Microsoft 365 Admin Center.

As a community moderator, I do not have the ability to modify the product's internal code or investigate specific tenant-level security logs. By opening a "Service Request," your organization can provide logs to Microsoft engineers who can identify the exact security patch or architectural change causing the conflict. This is the only way to resolve the issue permanently while still meeting your organization's security requirements.

I hope this provides a clear path forward for your team!