Access Blog:
Here's a summary of the issues fixed in the latest Current Channel build of Access, including a round of improvements to Zoom:
Zoom and display
Bug Name | Issue Fixed |
|---|---|
| Mouse event coordinates were wrong while a button was held on a zoomed form | On a zoomed form (any zoom level other than 100%), the X and Y coordinates passed to mouse event handlers such as MouseDown and MouseMove reported incorrect values while a mouse button was held down. This broke drag-and-drop and other mouse gestures that customer apps implement in VBA using those coordinates. Mouse event coordinates now report correctly at all zoom levels, including while a button is held. |
| Tooltips (ControlTipText) did not scale with form zoom | When a form was zoomed, ControlTipText tooltips continued to display at their normal, unzoomed size. Because ControlTipText is a form property, the tooltip text now scales together with the form so it stays proportional to the zoomed controls. |
| Tooltips stopped appearing for controls near the bottom of a form when zoomed in | At zoom levels above 100%, ControlTipText tooltips stopped appearing for controls near the bottom of a form. Tooltips now appear for all controls at every zoom level. |
| Rich-text fields did not resize or scale when zooming in datasheet view | When zooming while editing a rich-text field in a datasheet, the in-place editor was not resized or repositioned correctly and its text did not scale. Rich-text fields now resize, reposition, and scale correctly when the zoom level changes. |
| Showing or hiding controls through VBA left display artifacts when zoomed | When controls were shown or hidden through VBA at zoom levels other than 100%, the form was not fully repainted, leaving stray or overlapping controls on screen until the zoom level was changed. Showing or hiding controls now repaints the form correctly at all zoom levels. |
| Only the selected rich-text control scaled on a zoomed form | On a zoomed form with multiple rich-text controls, only the control currently being edited scaled correctly while the others rendered at 100%. All rich-text controls now scale to match the form's zoom level. |
| Checkbox focus indicator did not scale with row height in datasheet view | In datasheet view, when a row's height was increased, a Yes/No checkbox scaled to fill the taller row but the focus indicator (the dashed box drawn inside it) continued to draw at the original size. The focus indicator now scales together with the checkbox. |
Accessibility
Bug Name | Issue Fixed |
|---|---|
| Keyboard focus left the Zoom out button after reducing zoom | When reducing the zoom level using the Zoom out button in the status bar, keyboard focus moved to the form canvas instead of staying on the button, making it hard to zoom out repeatedly with the keyboard. Focus now remains on the Zoom out button after each use. |
| Screen reader did not announce inserting a control in Form Design view | When inserting a control onto a form in Form Design view using the keyboard, screen readers did not announce that the control had been inserted. Access now announces the confirmation so screen reader users know the action succeeded. |
| Screen reader did not announce the selected zoom option in the Zoom menu | In the Zoom split-button menu on the Home tab, screen readers did not announce which zoom option was currently selected. The selected state is now exposed to assistive technology. |
🗄Data and other
Bug Name | Issue Fixed |
|---|---|
| Copying a large amount of text from a text box copied only part of it | When copying a large amount of text from a text box (for example, several hundred lines) to another application, only a portion of the text was placed on the clipboard. The full contents of the text box are now copied. |
| Exporting a report to PDF could show a false "not enough free memory" error | When exporting a report to PDF, Access could incorrectly display the message "There isn't enough free memory to update the display. Close unneeded programs and try again", even when plenty of memory was available. The report now exports to PDF without this spurious error. |
| DateTime2 columns showed fractional seconds by default | DateTime2 columns (in local tables or linked SQL Server tables) displayed seven fractional-second digits by default, even with the Format set to General Date or left blank, so they looked different from DateTime columns. DateTime2 columns now display the same as DateTime by default, without fractional seconds, while explicit format strings continue to work as before. |
Source:
