Recommended: Excellent MS Access TreeView Control by Marcus Dieterle
Hi everyone, I just wanted to share an amazing resource I found for anyone looking to modernise their MS Access applications. The TreeView control developed by Marcus Dieterle (DIETERLE programmierung) is absolutely top-tier! If you are tired of dealing with the constant compatibility headaches, crashes, and bitness issues (32-bit vs 64-bit) of the traditional Microsoft ActiveX TreeView, this is the ultimate alternative. It looks modern, runs incredibly smooth, and is beautifully documented.Highly recommended for anyone trying to take their Access GUI to the next level. Publisher: DIETERLE programmierung Website: dieterle-programmierung.de Support: email address removed for privacy reasonsExplore and edit Microsoft Access databases (.accdb / .mdb) directly from VS Code.
Hi everyone, I'm looking for a way to move away from the native Access VBE and start using Visual Studio Code as my primary text editor. I mostly want to leverage its modern features like Dark Mode, multi-cursors, and better shortcuts. During my research, I came across the "Access Explorer" extension, which claims to let you "Explore and edit Microsoft Access databases (.accdb / .mdb) directly from VS Code". Before I risk running this on any live database, I wanted to ask the community: How stable is it? Does it work well for daily development? Is there any risk of database corruption when it saves and injects the edited code back into the .accdb file? How does it handle form/report class modules (Form_FormName), or is it only reliable for standard modules (.bas)? If you have used this extension or have a smooth alternative workflow to read/write code directly between VS Code and Access without manual copy-pasting, I would love to hear your thoughts!Fixes in Microsoft Access – Version 2608 (Build 16.0.20326.20100)
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.
Cloud Policy Service needs a Powershell module
I just started using the Cloud Policy service capability in the config.office.com portal. A Powershell module is sorely needed, in part because the UI a) can be slow and b) is uninformative in that the Policy Configuration Review/Summary is too high level and there is no comprehensive reporting of configured configurations and/or policies. Cmdlets that could extract the configurations and for each configuration, it scope, the policies that are configured and their configuration setting; list of all policies and policy configuration where they are configured would be very useful. Even better would be a cmdlet that can assess the policies applicable to a specific user and the 'route' the Cloud Policy Service took to determine them would be very useful in identifying why a particular behavior took place or didn't. This differentiate between device and web apps, where appropriate.
New Outlook: "Changing the ImapRemoteServerInfo is not allowed" after host migration
Hi everyone! I've migrated my domain/mailbox from one IMAP host to another in May. It cannot be added to New Outlook for Windows — fails instantly with INVALID_CREDENTIALS INTERACTION_REQUIRED, even when I deliberately enter a wrong password (so it's failing before authentication is even attempted). Using DevTools (olk.exe -devtools), the Network tab shows the real rejection from Microsoft's backend: Changing the ImapRemoteServerInfo is not allowed. Attempted to change it from imap.olddomain.sk to imap.newdomain.sk So New Outlook has a cloud-mailbox / connected-account shadow record for this address, pinned to the old host from a previous add attempt, and the backend refuses to update it. What I've confirmed: Webmail and a second mailbox on the same domain/host both work fine → not credentials, not the host. The account does not appear in Settings → Accounts (so I can't use "Remove from all devices" which worked on my first account). It's on no other device or client. App reset didn't help (record is server-side, not local). It's been ~7 weeks, so any 30-day inactivity purge hasn't cleared it How do I get this stuck cloud-mailbox / connected-account record purged when it isn't attached to any removable account? Is there a way to force it, or does this need Microsoft backend action?
Own domain flagged as harmful by Safe Links — submissions return "Unknown"
Our organization's own domain is being flagged as "This message contains a link that might be harmful" in Outlook and Teams. We submitted the URL for review via Submissions → URLs twice (over several days apart), and both came back as "Unknown - We checked but can't make a decision right now." We also tried adding the domain to the Tenant Allow/Block List, but the warning in Teams still persists. Per the portal notice, tenant allow entries only override bulk/spam/regular phishing verdicts, not malware/high-confidence phishing — so we suspect the domain may be misclassified at a higher severity level. Has anyone experienced this before, or know how to escalate when submissions repeatedly return "Unknown"? Submission IDs for reference: 5483d45c-405e-46c8-97e3-08df0cc793fb (Sep 7) and dcaab607-4ead-4791-4996-08df0a6ab25a (Sep 4).My printers don't work after I reinstalled Microsoft 365
I recently had to reinstall Microsoft 365. The software now works quite well, but I can't print a document in Microsoft Word or from anywhere in Windows 11. I have two printers: an HP Envy Inspire 7900e AIO and a Brother HL-L2420DW. Both printers worked before the reinstall, and both printers work without any problems on the Mac side of my laptop. (I use a Mac with Parallels to run Windows 11.) When I try to print from MS-Word in Windows 11, I select a printer from the list in the Print dialog. Then I have to wait for a printer connection. A few seconds later, I get a notice that the printer is "in an error state." My first thought was that I'll have to reinstall my printers in Windows 11, but I went looking for help. An AI helper I've consulted a few times walked me through a labyrinth of steps to fix the problem. The steps involved using the Command prompt or PowerShell (Administrator), but so far I've not had any luck. Seems to me I'll do as well by simply removing and reinstalling the printers. But that thought brings up more questions. I installed both printers using the manufacturer's instructions. For example, the HP AIO I installed with the full-feature software. My question: Do I need to do anything special before I reinstall the printers? Do I simply go to Printers & Scanners and delete my printers and then reinstall them? Also, will any of this affect these same printers on the Mac side?
Microsoft Places individual desk booking is not working
Hi, Following the documentation, https://learn.microsoft.com/en-us/microsoft-365/places/configure-desk-booking, I successfully ran the shared command lines without any errors. However, on Microsoft Places, I am unable to see individual desks appear; only desk pools are visible. Has anyone managed to get this to work? Thanks,
