Fixes in Microsoft Access version 2608 Build 16.0.20326.20100

Brink · 2026-09-09T16:41:43-0400

Access Blog:

Version 2608 was first released to Current Channel on August 18, 2026. Here's a summary of the issues fixed in this release, including another round of improvements to Zoom.

Important update: A regression introduced by an earlier security update could cause labels, text boxes, combo boxes, and other controls to lose their fonts, colors, or styles after printing or previewing reports that contain embedded images or OLE objects. It could also contribute to crashes during printing or PDF export. This issue is fixed in Version 2608 Build 16.0.20326.20132, released September 1. We recommend updating to this build or later.

Zoom

Issue	Fix
VBA Zoom did not work reliably with popup forms	Setting or reading a popup form's Zoom property through VBA could use the currently active document window instead of the form named in the expression. VBA now applies the Zoom property to the intended popup form.
Zoom set during Form_Open was replaced by the default zoom	When Form_Open code set the form's Zoom property, the default zoom-on-open logic could immediately overwrite it. Access now preserves the zoom level selected by the form's VBA code.
Combo boxes could show blank rows or reject selections at some zoom levels	At some zoom levels, a combo box could leave blank rows in its drop-down. At very low zoom levels, some values also could not be selected directly. Combo boxes now size and respond correctly as the zoom level changes.
Zooming out a large report could leave display residue	At low zoom levels, a large report could leave stale content at the bottom of the Report View window. The report now repaints the full window correctly after zooming out.
Control borders became too thick below 100% zoom	Borders could appear disproportionately thick when a form or report was zoomed below 100%. Border rendering now remains visually consistent at lower zoom levels.
Drag selection in a zoomed datasheet could use the wrong coordinates	When selecting a rectangular range by dragging in a datasheet at a zoom level other than 100%, Access could mix screen and document coordinates and hit-test the wrong cells. Drag selection now uses the correct coordinates at every zoom level.
The 25% Zoom keyboard shortcut was difficult to use	The keyboard shortcut for 25% zoom now uses the 2 key instead of requiring the percent-sign key combination.
Existing applications needed a way to disable built-in Zoom	A database-level option is now available to disable built-in Zoom when an application already provides its own zoom commands or keyboard shortcuts.
The screen-reader Zoom announcement was not localized	The announcement of the current zoom percentage used a hardcoded English phrase. It now uses localized text and word order for the selected Office language.

Forms and reports

Issue	Fix
The date picker appeared for locked or read-only controls	The date-picker icon could appear for a locked or read-only text box even though its value could not be edited. The icon is now hidden when the control cannot accept a date selection.
Tab and Shift+Tab could change control stacking order in Design View	Using Tab or Shift+Tab to move between controls in Form Design View could unexpectedly change their front-to-back order. Keyboard navigation now leaves the control stacking order unchanged.
Horizontal report lines disappeared in some Version 2608 preview builds	Some customers who received early preview builds of Version 2608 found that horizontal Line controls with a height of zero appeared in Report View but disappeared in Print Preview, printed output, and exports. This was corrected before the general Current Channel release, and these separator lines render correctly in all report views and output formats.

Queries and data

Issue	Fix
The modern SQL editor could show an incorrect insufficient-memory error	Executing a query in the modern SQL editor could display "Insufficient memory to perform this operation," typically on the first execution in an Access session. Queries now run without this spurious memory error.
The query No Format setting could disagree with Object Properties	For some query types, including crosstab and delete queries, the No Format value shown in the property sheet could differ from the value stored in Object Properties. Both locations now display and save the same setting.
Calculated SharePoint columns displayed #Error in linked tables	Calculated columns from a linked SharePoint list could display #Error instead of their calculated values. Access now displays the values correctly.

Customization

Issue	Fix
Property Sheet font size can now be adjusted	Access Options now includes a setting for changing the font size used in the Property Sheet, making its text easier to read on high-resolution displays and for users who prefer larger text.

Source: