My spidey-sense is tingling! (and not in a good way)
Access MVP Alum Gina Whipp has reported a series of issues with Access version 2204
• Property not found
• No current record.
• The search key was not found in any record.
• The object doesn’t contain the Automation object ‘YourControlName’ (And while that is control on the Form it is not used in the code anywhere. Oh, and yes that is the way it is spelled in the message but not on the Form.)
and then we see reports like:
I tried the front/backend files on two PC's I have that are running Office 365 and they too have the same issue.
It seems like Microsoft has broken things.
Is anyone else having issues after today's update?
Could not understand, since years this application was working fine, no such error was happening before the Office 365.
Have never gotten that error before. I tried compacting and repairing the database. The errors are still popping up.
No changes have been made to any code of the affected forms for at least a month.
The BE db has had Compact and Repair done on it.
I...
So be forewarned, patch Tuesday is upon us and things are about to get ugly in the coming days as the latest update(s) get deployed and more and more users start experiencing such issues.
If you’re running the Current Channel for Office Updates, I strongly urge you to switch. Microsoft’s track record for bugs in their releases speaks for itself (a small listing can be found at Does Microsoft Access Have a Future?) and you really should sadly switch to Semi-Annual Enterprise Channel for stability.
If you do start seeing problems, please post a comment below so we can confirm the issue is widespread, inventory all the variations and then I can then report them back to Microsoft. Thanks.
Note that although Microsoft seems to think they resolved the issue, people are still reporting the same errors (see comment section below).
And yes, Microsoft does have the ability to make changes to your installation without your knowledge or intervention. This was confirmed in a public forum by a member of the Access Dev Team during a discussion regarding another bug. So even stopping updates doesn’t guarantee no changes occur on your PC! There is simply no means to insulate/isolate/lock-down an application anymore.
Let me know what you are seeing. Has it been resolved or are you still experiencing errors?
Yes code that has been running for 20 years has started throwing up the “no current record” error. The program seems to continue working correctly, just the message appearing.
It occurs with both 32 bit and 63 bit versions of Office/Access.
64 Bit – Version 2112 Build 16.0.14729.20254
32 Bit – Version 2204 Build 16.0.15128.20128
We are having the same problem after the update to 2204
• Property not found
• No current record.
which is very annoying
Set-up – Database front end runs on the individual PCs and data tables are held on linked database on a server.
Issue – When closing a form attached to a table, the “Property not found” warning box is displayed after the form is closed. It only occurs if a record attached to the form as been opened. If changes are made, the data is stored and no data is lost.
The message is not displayed if the form is opened and then closed with no record being accessed.
This only appeared in the last week and only affects one form at the moment.
Thanks DP, always good to have an explanation before it is needed.
👍 🤣
Daniel,
Thank you for jumping straight on this one and creating a valuable focus point for updates.
However I fear that this is more complicated than the usual Patch Tuesday problems.
One of my clients started reporting this yesterday May 10th here in the UK. They were running build 15128.20178 and had been since May 2nd. But the problem didn’t occur until yesterday and now it is crippling them.
Furthermore, I rolled back to build 15028.20224 (April 26) and it did not fix the issue.
I have clearly evidenced that this is being caused by code running “under the hood” as a form closes. Details in the first thread you refer to above.
Kind regards
Neil
God only knows! It is very coincidental that people suddenly started having issues Patch Tuesday, but then again Microsoft does control things at their end (requiring no updates or user interactions) which directly impact Office/Access. Time will tell, but there is definitely a problem and it is only getting worse with time.
As I have said in the past, it looks like Access is bursting at the seams every time MS rolls out an Office update. Our 32-bit 2010 MSI apps have been happily humming along for years, except for that 2019 “query is corrupt”, while we have been watching everyone else that uses 2013+ C2R versions experiencing frequent interruptions associated with Office updates. Are we having fun yet?
Access code that has been unchanged for 12 months, started throwing “No Current Record” when closing certain forms. Access Version 2004 Build 15128.20178, running on Windows 10. Problem started this morning 11th May 2022
I’m also getting untrappable “No current record” error when I close certain forms. I managed to pinpoint the exact line of code in two instances that caused this error, and both instances had to do with subforms and the Recordset object.
1. In a subform’s Current event, I originally had Me.Recordset.RecordCount. I changed it to Me.RecordsetClone.RecordCount, and that prevented that particular “No current record” from showing up.
2. In another form module inside another database, I referenced a subform with Me!MySubform1.Form.Recordset.FindFirst “[Field1]=’some critera'”. Remarking that line out immediately prevented the “Property not found” error from showing. Unfortunately I can’t use RecordsetClone here because FindFirst only works with Recordset.
Just to let you know, FindFirst used to work with RecordsetClone. I used it for years then found that it no longer does. It appears to be because the RecordsetClone created (literally a Clone of the Recordset) is not postioned at first record. You now need to do that yourself by inserting:
With Me.RecordsetClone
If Not .BOF Then .MoveFirst
.FindFirst “JobTypeCode='” & strJobTypeCode & “‘”
If .NoMatch = False Then
Me.Bookmark = .Bookmark
End If
End With
Hey, they seemed to have fixed it! Right after my previous post. Now I don’t get these weird untrappable run-time errors anymore. I still got a strange “Bad DLL calling convention” when no DLL was called in the procedure where the error occurred. I had to decompile my database with the /decompile command-line option, then do a compile to get rid of that error.
Ive had a DB running for years with no issue.
As each of my users udates to latest office on May 10th 11th … they starte to experience the no record found, message.
Also the DB would close with one particular ‘on click event’ button that hasnt changed in years.
How do we get the magic fix that some people seem to of got?
It just appears, there is no way to force it (to my knowledge). It’s out of our hands and in the hands of Microsoft, sadly.
Thanks Dan P 🙂
So, the magic fix has just arrived for us! Users did have to close & re-open Access for it to work.
Just glad i wasn’t in the middle of developing when this arrived …. as wouldn’t assume it was a MS Office created issue .. and still be questioning my code & application.
Every days a school day!
Im still having the issue with verison 2205 build 15225.20092. Windows 11 pro. It only seems to be on the windows 11 machines in our business, so far!
From the Access Dev Team: “15225.20092 is a preview build, if they move to current channel that should resolve the issue.”
PS: Never run a production system on the preview build, or even the current channel! (It’s too volatile IMHO)
Thank you. I wasnt aware there were even different channels!