and had to tweak my code that involved Recordset, like the posters did above. But note that this had nothing to do with Recordset
+
Just updated 365 again to 15128.20224. All still OK it seems
+
Interesting. I've had 365 v2204 build 15128.20178 for a while on several workstations and still haven't experienced this bug. Lucky me!
I tried the example app from post #32 and it works for me without error.
I guess maybe I should pivot to simply trying to say it's a matter of perspective.
I, for one, after reading decades of posts about Windows Update (about half of which are really the fault of Windows Update, and half of which are not), have come to conclude that sometimes, we
might be too quick to blame Windows Update.
I see it very similar to when a poster comes along and says stuff like: "Access gets angry when I try to open a SQL Server recordset".
No, Access does not get angry. There is a way to do it and if it doesn't work there is an actual reason it's not working.
If Windows changes their operating system to disallow default permissions to local users on %AppData\Roaming%, or something, my code might suddenly "stop working". Also, I didn't put in place anything to check whether they did or didn't have permissions to that folder, and proceed to handle it appropriately - like use a different folder. In this context, is it fair to simply say: "Windows Update broke my database" - and that's it?
Not really, I don't think, it's a matter of perspective. That may not even be the best example, but you get the point.
Another piece of evidence to consider is some people's databases all seem to break on every Update, others hardly ever if ever do.
There may be several reasons for that, but I think we'd be prudent to consider what
all of those reasons may be...
Because of human nature, we tend to only consider the reasons that paint us in a good light as developers, and Windows as the bogeyman/culprit.
I think it's clear by this point that my reasoning goes something like this: Everyone's code is based on assumptions...The question becomes how reasonable those assumptions were.
Yes, Windows Update sometimes just breaks things with no defense, explanation or justification.
No, that's not the case every time a Windows change breaks your code.