Microsoft Access Monaco Editor Fixes 2510 2602: Undo, Contrast and Datasheet Improvements

Microsoft’s Access team has quietly continued the steady work of hardening the app-layer pieces of Microsoft 365, shipping a string of targeted fixes that remove persistent friction for database designers and SQL authors — most notably tweaks to the Monaco SQL editor and a set of visual and selection fixes in Datasheet and designer views that have been irritating users for months. The officially published Access 2510 notes document important fixes (Undo/Redo for Z‑order operations, improved keyword contrast in dark themes, and Waterfall chart connector visibility), while more recent community and news reports indicate the 2602 family includes further Monaco and datasheet corrections. ([techcommunity.micrchcommunity.microsoft.com/blog/accessblog/access-bug-fixes-version-2510-build-19328-20158/4467552)

Background / Overview​

Microsoft began rolling out the modern Monaco-based SQL editor for Access in late 2024 to align Access’s SQL editing experience with other Microsoft developer products (VS Code, SSMS) and to deliver advanced editing features — syntax highlighting, line numbers, color themes, and richer editing commands. Early adoption brought benefits but also a steady stream of visual and behavioral regressions as the Monaco integration matured. The Access team has been publishing concise bug-fix posts for each version; the 2510 release is one of the clearer examples of small, high‑value corrections shipped to the Current Channel.
Alongside Microsoft’s posts, independent trackers and community blogs have been cataloging Monaco’s issues — from formatting behaviors that change passthrough queries to WebView2 memory patterns and view-switching artifacts. Those third‑party trackers have proven useful to surface real‑world reproducible problems and to track the rollout of fixes across Insider/Beta and Current channels.

---

What changed (concrete fixes and reported improvements)​

Version 2510 (Build 19328.20158) — official Microsoft fixes​

Microsoft’s Access blog enumerates three headline fixes delivered in the 2510 family:

• Undo/Redo for Bring To Front / Send To Back — designers can now reorder controls on forms/reports and use Undo to revert those stacking changes. This fixes a long‑standing frustration when tweaking layout z‑order.
• Monaco editor keyword contrast in dark Office themes — keywords in the Monaco SQL editor were previouslyicient contrast in dark themes; keywords are now painted in a lighter blue to improve legibility. This is an accessibility and usability improvement for long edit sessions.
• Waterfall chart connector visibility — connector lines in Waterfall charts could be too thin or hard to see in some presentations; the update exposes a thickness control so connectors are readable.

These small changes are classic “quality of life” updates — they don’t add big new features but reduce the friction that causes repeated workarounds and subtle errors. The same 2510 fixes were also summarized in community threads and trackers that monitor Access’s monthly notes.

Reported updates in the 2602 family — passthrough formatting and datasheet selection (community / press reports)​

More recent coverage — including a WindowsReport piece and community trackers — reports additional fixes in the 2602 update cycle (Current Channel build 19725.20126 is referenced by multiple community sites as the Office/365 build that carries the patch batch). Those reported changes include:

• Passthrough queries no longer auto‑formatted by Monaco — previously, Monaco’s “expanded” autoformatting could reflow or inject whitespace into passthrough (server‑side) SQL, which is dangerous because passthrough SQL is delivered verbatim to the remote engine and even small formatting changes can break vendor‑specific syntax. Community sources report the editor now disables automatic expanded formatting for passthrough queries, preserving the exact SQL as authored.
• Monaco font-size unit conversion fixed — an incorrect conversion made Monaco text appear slightly larger than the Access-configured font size; the reported fix aligns the editor’s rendering with the chosen font size.
• Datasheet selection visual artifact corrected — a visual bug allowed users to drag a selection beyond the last column into the empty datasheet area and then see a persistent highlight that lay outside actual table boundaries; the update reportedly clips selection behavior and removes the over‑extended highlight.

It’s important to note that the Microsoft Community Hub post archive had published fixes through version 2601 as of mid‑February 2026, and the 2602 Access‑specific bug page either appears later or is rolling through channels; community reporting and forum posts corroborate the existence of the Office build 2602 family and its general rollouts. In short: the official 2510 fixes are confirmed by Microsoft, while the 2602 Monaco/datasheet claims are reported by Windows/press and community trackers and align with what independent Access trackers logged as fixes in Beta/current previews.

---

Why these fixes matter (practical impacts)​

• Passthrough SQL is fragile: Passthrough queries are the canonical way to run database‑engine‑native SQL from Access (for example, Oracle, MySQL, SQL Server). They should be treated as source code that Access must not touch. Automatic formatting that alters whitespace, line breaks, or comment layout can change how a remote parser handles the query (or how vendor extensions are interpreted). Disabling automatic expanded formatting for passthrough queries reduces a real regression risk for administrators who rely on precise, engine‑specific SQL.
• Designer confidence & speed: Losing Undo/Redo when tweaking z‑order is more than an annoyance — it slows iterative layout work and forces designers to rebuild arrangements or keep manual notes. Restoring reliable Undo/Redo streamlines rapid prototyping of forms and reports.
• Developer ergonomics and accessibility: Monaco brings a modern editing interface to Access, but only if token colors, font rendering, and keyboard behavior are predictable. Fixing contrast and font sizing reduces eye strain and misreadings, particularly for those using dark themes and working long hours.
• Visual correctness in datasheet view: The datasheet is the most frequently used interactive surface in Access. Visual artifacts in selection and totals rows can lead to misinterpretation of results or unnecessary help tickets. Fixing selection clipping improves the fidelity of the UI to the actual data.

---

Cross‑checks: what’s official, what’s community‑reported​

• Official Microsoft Access blog posts explicitly list and describe the fixes shipped in the 2510 release. These are the most authoritative, granular confirmations for the Undo/contrast/Waterfall fixes.
• Microsoft’s consolidated bug summary covering versions 2511 through 2601 documents a broader cross‑section of Monaco issues and their fixes up through early 2026, indicating an ongoing cadence of iterative corrections. That Microsoft timeline is essential for provenance when claims are incremental.
• Community trackers and chroniclers that specialize in Access (examples include independent blogs and trackers that compile reported issues and the channel builds where they were fixed) provide rapid visibility into Beta/Insider rollouts and are often the earliest public signal that a fix has reached Beta or Current channels — they documented that passthrough formatting was scheduled to be disabled in Beta 2602 and then observed in subsequent channel builds. These independent trackers corroborate press coverage and Microsoft’s public notes when official posts lag the rollout.
• Press sites and news aggregators covering the Office 2602 Current Channel build (19725.20126) corroborate the build number and the fact that Office apps across the suite received service updates on the same cadence. However, Access‑specific reporting for 2602 often originates in community posts and niche Access trackers rather than a Microsoft “Access‑only” post on the same date, so readers should treat press claims as accurate but confirmable.

Caveat: when Microsoft has not yet published a dedicated Access blog entry for a specific build family, community and press claims should be treated as reported and corroborated by trackers, and flagged accordingly. Where Microsoft’s own Access blog is explicit (like 2510), that is primary evidence; where Microsoft’s consolidated posts extend only to 2601, later 2602‑family claims are best described as reported but awaiting an explicit single‑app confirmation.

---

Risks, remaining caveats, and how to protect projects​

• Autoformatting has side effects. Even with Monaco behavior adjusted, any automatic formatting feature carries the risk of invisible changes (non‑breaking whitespace, different newline sequences, or comment normalization) that might affect version control diffs, checksum validations, or vendor‑specific SQL. Always keep original copies of passthrough SQL outside Access (for example, in source control or external SQL files).
• Channel timing and rollouts. Fixes often arrive in Beta or Insider channels first. Admins who need stability should not assume a Current Channel update contains every fix reported by community trackers until Microsoft publishes the Access‑specific post or the enterprise update documentation. Use staged testing to catch regressions.
• Monaco is powered by WebView2; memory/instancing considerations remain. Community reports during the Monaco rollouts documented WebView2 process patterns (additional processes per open query) that can affect memory profiles. While many of those issues have been mitigated, administrators on memory-constrained devices should monitor resource usage after enabling Monaco.
• Visual artifacts may recur with theme or DPI changes. Fixes for font‑size conversions and contrast address the most visible problems, but mixed DPI setups and third‑party high‑contrast themes can reintroduce rendering anomalies. Test across common configurations.

---

Practical guidance: what users and admins should do now​

Quick checklist for individual users​

• Confirm your Access/Office build: open Access → File → Account → About Access (or About Microsoft 365 Apps). Note the Version and Build number and record it.
• If you rely on passthrough queries, export or copy the SQL text to a versioned file (source control) before editing in the Monaco editor. That preserves the canonical SQL should any editor action alter formatting.
• If you see Monaco‑related problems, temporarily disable Monaco for the affected database: Monaco can be toggled in Access Options or programmatically (the Access team documented how to enable/disable the new editor). Test behavior with Monaco off to isolate the issue.
• After updating, rerun critical passthrough queries and stored routines in a development or staging environment to confirm no semantic changes occurred. Treat formatting changes as a potential red flag.

Steps for IT and DBA teams (enterprise)​

• Stage the new Office/Access build in a test ring before broad deployment. Use representative databases, linked servers, and passthrough queries as part of acceptance tests.
• Update your runbooks to include: capturing Access build numbers, saving source copies of passthrough SQL, and verifying datasheet visuals for heavily used tables and totals rows.
• If you rely on long‑running Access applications, consider deferring Current Channel updates via administrative controls until the relevant Access bug‑fix post appears or until you have run a controlled pilot. Microsoft provides update channels and management controls for enterprises.
• Where Monaco is problematic for large‑scale deployments, evaluate toggling Monaco off at the database level during a controlled pilot and collect feedback from power users.

---

How to verify whether you have the fix (short verification scripts and tests)​

• Verify Monaco passthrough formatting protection:
• Copy a known vendor‑specific passthrough SQL (with tricky whitespace/comments) to a plain text file.
• Paste it into a passthrough query in Access and save.
• Close and reopen the query in SQL view. If the editor has disabled automatic expanded formatting for passthrough queries, the pasted text will remain byte‑for‑byte identical (visually identical is usually sufficient; for strict verification use a text comparison of the saved SQL against your source file).
• Verify datasheet selection clipping:
• Open a table in Datasheet view.
• Click and drag beyond the final column into the empty datasheet area and release.
• Confirm the highlight disappears and selection is limited to existing columns. If a highlight persists outside the table border, the visual bug remains.

---

Long‑term perspective: Monaco, Access modernization, and trade‑offs​

Monaco brings Access closer to the modern developer ecosystem: shared editor primitives, improved tooling, and a bridge to VS Code conventions. That alignment benefits SQL authors used to other Microsoft editors. At the same time, the integration adds complexity (WebView2 instances, editor formatting features, theme/unit‑conversion interactions) that must be carefully integrated into a legacy app with idiosyncratic behaviors (e.g., passthrough queries, Access‑specific SQL quirks).
The Access team’s incremental fix cadence — small, focused updates addressing specific regressions — is the pragmatic approach for a mature product family. It reduces wide‑scale risk but does require users to remain vigilant with version tracking and to use staging/testing practices typical for enterprise apps.

---

Recommendations (concise)​

• If you’re a power user or developer: Back up passthrough SQL externally; confirm your Access build; test critical queries after upgrades. Consider temporarily disabling Monaco if you require absolute preservation of query formatting until you can confirm the fix in your environment.
• If you manage Access across many users: Pilot the new build in a test ring; update policies and deployment pipelines to include verification steps for passthrough queries and datasheet visuals; stage rollouts via existing channel management tools.
• If accessibility and readability matter: Encourage users to adopt the corrected dark‑theme rendering; confirm that theme + DPI combinations used by your team display keywords with adequate contrast.

---

Conclusion​

The Access team’s recent fixes are small in scope but meaningful in practice: restoring predictable Undo behavior, improving Monaco’s dark‑theme contrast and font fidelity, and removing formatter interference from passthrough SQL all remove friction from daily Access work. Microsoft’s own posts confirm the 2510 fixes, while community trackers and press coverage corroborate the broader 2602‑family corrections that target Monaco formatting and datasheet visual behavior. Administrators and power users should treat these updates as welcome progress but continue standard precautions: stage the update, version passthrough SQL outside Access, and verify critical workflows in a controlled environment before wide deployment. If you encounter unexpected behavior after upgrading, reproduce the issue in a test database, toggle Monaco off to isolate the problem, and report the finding through your Microsoft support channel so the product team can act — the Access rollout model depends on feedback from real‑world scenarios to prioritize and lock down fixes.

---

Source: Windows Report https://windowsreport.com/latest-microsoft-access-version-fixes-monaco-editor-and-datasheet-bugs/