We may have another issue to watch out for this week. A couple of users have now reported that installing KB5064081 is causing their Access applications to crash, specifically when running code that uses ADO and/or DAO.
Continue reading
Huston we have yet another problem!
We are seeing multiple reports that a recent update has broken, at the very least VBScript.RegExp, resulting in the following error:
I have seen 3 reports today alone of version 2506 causing issues with Access, so be forewarned.
Continue reading
I was part of a forum discussion where it was shared that:
This affects any feature that makes use of the wizard including MVFs and lookup fields at table level
This is a short post to advise you that there is a new bug affecting Microsoft Access where some or all command buttons may not display their labels and some also indicating images don’t render either!
Multiple forum threads have already reported this issue across various Access communities impacting Version 2506. Below are some of the specific build no. some users have mentioned as impacted by this issue:
During a recent project, I encountered an intriguing quirk in Microsoft Access that’s worth sharing. This peculiar behavior occurs when mixing ADODB and DAO recordsets in form events, leading to unexpected results that could easily be mistaken for database corruption.
I initially created a form with a dynamically built ADODB recordset in the Form_Open event:
Private Sub Form_Open(Cancel As Integer)
Dim rstVirtual As Object
Set rstVirtual = CreateObject("ADODB.Recordset")
With rstVirtual
.Fields.Append "ItemId", 20
.Fields.Append "ItemDescription", 200, 50
.CursorType = 3 ' adOpenStatic
.CursorLocation = 3 ' adUseClient
.LockType = 3 ' adLockOptimistic
.Open
End With
'...
Set Me.Recordset = rstVirtual
End Sub
Well, I’m all for reminiscing, but in this instance I think the Dev Team may have gone a little too far!
A user recent left me a comment inquiring about how they could export an Access report in Excel format, but as an xlsx. Seem like a reasonable enough question considering the xlsx file format has been the default format for at least 17 years now!
Once again, in the category of ‘you can’t make this crap up’, I was trying to connect to a new client’s SharePoint site via Access to review their data and determine how I could clean things up and get them setup properly in Azure…
Well, using the External Data -> More -> SharePoint List and entering the SharePoint URL, I was prompted for my credentials after when I go to authenticate, this is what I get!
There isn’t much information at this point in time on the root cause and no official fix to the issue (there are workarounds however, see below), but it would seem that with the most recent update(s) Microsoft Access no longer closes properly and leaves instances of the msaccess.exe running in the background.
There may be a new Microsoft Access bug in the air as I have seen a couple recent mentions of Access default folders not working as they historically did.