I ask you:
What is the purpose of the Microsoft Access ‘Fixes or workarounds for recent issues in Access’ webpage/portal?
The reason that I ask this today is that we have seen a number of bugs, both past and present:
I ask you:
What is the purpose of the Microsoft Access ‘Fixes or workarounds for recent issues in Access’ webpage/portal?
The reason that I ask this today is that we have seen a number of bugs, both past and present:
Reporting bugs will become my full-time job thanks to Microsoft!
So there are new reports that version 2206 also breaks iterating over .Fields,
The gist of it being that it no longer returns .Field2, but rather .Field3 object breaking existing code.
You can read for yourself all the details by reviewing the Stack Overflow thread on the subject:
I notified Microsoft about the issue, as have other MVPs I believe.
Microsoft has since confirmed the issue and suggested:
The simplest workaround for now is to change declarations of type DAO.Field2 to DAO.Field
Yep, one more to add to the long list Microsoft Access bugs!
As reported:
We seem to have a new bug that has surfaced in version 2206 (build 15330.20196) in which reports don’t seem to be properly rendering.
Microsoft has supposedly fixed the issue by flipping flags at their end. So you need not do anything beyond close and restart Access.
Yes, it’s like magic. Microsoft can remotely alter your installation without your knowledge or consent.
Here’s a functionality that is often asked for:
How can I compact the current database via code (VBA)?
Typically the answer is either:

What if I told you there was a better way! Well there is!
I’ve been using Power Automate Flows for heading on 2 years now on an extensive project for one of my client’s and I thought I’d give people some more insight into my experience using them.
You can consult my original post on the subject:
I’ve used a number of connectors, such as:
and, in the process, interacted with numerous systems:
Here’s an interesting one. I was helping on Experts-Exchange with a question relating to copying a Microsoft Access database and then compacting it using PowerShell.
Personally, I’d use a bat or VBScript file to do this normally, but I still thought I’d share how it can be done via PowerShell for those of you that might need to do so.
I thought I’d share the solution I provided to a member in a recent UtterAccess thread:
It wouldn’t be a Microsoft update without a new Access bug! OMG.
As reported:
and now confirmed by fellow MVPs, build 15225.20288 breaks attachment fields causing Access to outright crash.
Once again, looking to provide clients with better features within my Access applications, I turned my attention to creating Organizational Charts.
In this instance, I used Google Charts, but as with all web driven solution there are a multitude of other libraries to choose from, it’s just a question of finding the one that makes you happy, or creating your own! Here are a few I came across while exploring creating Org. Charts should you ever wish to see what else may be possible:
<rant>
So what did I learn this week?
In short, don’t use Microsoft Azure Web Service to host your applications!
That’s right, don’t do it.
I had a client with a PHP application that was running on another host. He wanted to put everything under the Microsoft Umbrella and so we migrated the app. We’ve been very happy overall with the service for about 2 years and saw a nice boost in performance too (but that is more because the switched away from using shared hosting though).
So why am I advising you stay away from it then?