First Published 26 Feb 2026	Last Updated 6 Apr 2026

This article provides information about Access bugs and other issues reported during Feb 2026 (in order of date reported) including symptoms and action taken.
Once again, relatively few issues this month but with varying degrees of impact

IMPORTANT:
Insider channels (particularly Beta Channel) are used by Microsoft to test new features before these go to production channels.
It is to be expected that the insider channels may contain bugs. These channels should only be used for testing purposes and NEVER for production use.

Item	Bug information	Date Reported	Reported By	Action taken
a)	PDF files no longer open in the legacy IE browser control under Windows 11 Appears to have been caused by a Windows update - possibly KB KB5074109 released on 2026-01-13 which caused various issues e.g. with classic Outlook Workaround: Use the Edge browser control or rollback the January updates for Windows 11	2026-02-03	Karl Donaubauer	Windows issue (not Access specific)
b)	Office apps including Access do not close properly leaving hanging instances in Task Manager This is a periodic problem and may have many causes. For some users this may be due to Teams Integration with Office apps. See detailed article on this website. Workaround: Try changing TWO Teams settings: i)   UNTICK 'Register the new Teams as the chat app for Microsoft 365' in Teams settings. ii)   CHANGE 'Always open Word, PowerPoint & Excel files in' .... Browser (NOT Teams) NOTE: It may be possible to reverse these changes once the hanging instances problem has been fixed.	2026-02-08	Colin Riddington
c)	"Requested type library or wizard is not a VBA project" error when opening a Navigation Form containing code in an ACCDE Affects all versions from A2010 onwards for any navigation form with code in ACCDE files Workaround: Create an OnError event for the main navigation form - see the first link in d) below	2026-02-11	Philipp Stiefel	Being investigated by the Access team
d)	Issues swopping Edge browser controls for local / online files For security, the Edge browser control blocks swopping between local & online files. This is solved by using two controls. However setting the visible state to true when required doesn't work correctly for local files Workaround: Change the control height instead; setting it to zero when not in use.	2026-02-20	Colin Riddington	Acknowledged by the Access team

Related Articles:

a)   Various forum threads including:
      •   Thread at MS Learn: Unable to view PDF in form following January 2026 MS Access Update
      •   Another MS Learn thread: PDFs no longer render in Access Web Browser control after Jan 2026 update — only a gray screen
      •   Thread at Access World Forums: PDFs no longer open in the legacy IE browser control

b)   Article on this website: Teams Integration Causing Office Problems

c)   Numerous reports over the years including:
      •   Post at MS Learn from 2011 (with workaround): Requested type library or wizard is not a VBA project
      •   Blog post by theDBGuy from 2016: Requested type library or wizard is not a VBA project
      •   Post by Geirr at Access World Forums(Jan 2026): ACCDE - "Requested type library or wizard is not a VBA project"

d)   Thread by Kitayama at Access World Forums: Web Browser Controls : A never ending struggle



Bug fixes in Current Channel Version 2602 Build 19724.20126 (released 2026-02-24)

The Access team have published a blog article listing the following three Access fixes released in version 2602 (Build 19725.20126)

Item	Bug information	Issue Fixed	Related Articles
a)	Monaco query editor applied unwanted autoformatting to passthrough queries	The Monaco SQL editor was applying automatic formatting (such as adding whitespace or changing capitalization) to passthrough queries. Since passthrough queries are sent directly to the server's SQL engine without Access interpreting them, autoformatting could alter the SQL in ways that break server-specific syntax. Autoformatting is now disabled for passthrough queries, preserving the exact SQL as written.	Monaco SQL Editor - Changes, Issues and Fixes See Fixed Issues 31) Access Bugs & Issues Summary - Jan 2026 See Item b)
b)	Monaco query editor font size did not match Access settings	When using the Monaco SQL editor, the font size in the query editor didn't match the font size configured in Access's client settings. An incorrect unit conversion resulted in text appearing slightly larger than expected. The conversion has been corrected so the editor font size now matches the configured setting.
c)	Datasheet selection could extend past the last column	When selecting cells in a datasheet by clicking and dragging, it was possible to extend the selection rectangle past the rightmost column into an empty area. Releasing the mouse and then clicking elsewhere would leave the selection highlight drawn in that empty area, since Access did not erase the over-extended selection. The selection is now properly limited to the actual columns of the datasheet.

Feedback

Please use the EMail button in the contact form below to let me know whether you found this article interesting/useful or if you have any questions/comments.

Please also consider making a donation towards the costs of maintaining this website. Thank you

Colin Riddington	Mendip Data Systems	Last Updated 6 Apr 2026

Return to Bugs & Fixes Page

Return to Top