Although the majority of the world has moved on to advanced systems like SQL Server, Snowflake, Redshift, and other cloud platforms to meet their relational database management system (RDBMS) needs, there are some who still rely on relatively old software like Microsoft Access. Fortunately, Microsoft still supports this tool, and now, it has detailed all the bugs it fixed in the September 2025 release.
Bugfixes were made available to Version 2507 (Build 19029.20136) and Version 2508 (Build 19127.20154). We"ll start off with Version 2507 which received eight bugfixes, they are summarized below:
- Customers who were importing queries from older databases which had never been used with the Monaco SQL editor were receiving errors, but this should not be the case anymore
- Queries which had unicode characters were not being saved in the new Monaco SQL editor, this behavior has been patched
- Another issue with the new Monaco SQL editor was that you would get errors when running the Find Duplicates and Crosstab query wizards, this shouldn"t happen moving forward
- Pressing the F1 key in the new editor resulted in a crash, but it should now launch the context-sensitive help
- An error was thrown when referencing an OLE automation object in VBA code, Microsoft says that this was happening when the object was stored in an Unbounded Object Frame
- Crashes were occurring when opening queries directly in SQL view, this is now fixed
- Images should now display correctly on button and image controls
- Microsoft is deprecating the Salesforce connector, so it has added an advisory within Access about this change
The more recent version, which is 2508, received five bugfixes, these are detailed below:
- Control wizards were not launching when adding new controls to subform in design view, this should work now
- Access would crash when pressing F6 in Design View, but it will now allow navigation with forms
- Users can now select Large Number fields in the Find Unmatched Query Wizard
- All wizards previously throwing errors on 32-bit configurations should now work
- Some fields were being incorrectly encoded when exporting to HTML, this has now been patched
If you are still using Access, do keep in mind that Access 2016 and 2019 will run out of support within the next few weeks, so remember to upgrade to a supported version before then, ideally the variant present in Microsoft 365.