Joining this bandwagon ...
The June 2 update to Office 365 BROKE one of my apps. Somehow, what they did caused 15 year old DAO recordset code to break.
Set rs = to select * from local table started NOT GETTING ALL THE FIELDS!
Sorry for yelling but this ruined my Friday. Looking forward to at home happy hour.
Anyway, the fix was to roll back to December 2019.
There's a cool little PowerShell script on MS website that lets you pick a 355 version.
I hope this prevents someone from debugging perfectly good code.
Stay safe,
Steve Conklin
From: MSAccessProfessionals@groups.io <MSAccessProfessionals@groups.io> on behalf of Russ <grizpatch@twc.com>
Sent: Friday, June 12, 2020 3:31:40 PM
To: MSAccessProfessionals@groups.io <MSAccessProfessionals@groups.io>
Subject: Re: [MSAccessProfessionals] [IMPORTANT] Windows 10 update May 2020 is buggy
Sent: Friday, June 12, 2020 3:31:40 PM
To: MSAccessProfessionals@groups.io <MSAccessProfessionals@groups.io>
Subject: Re: [MSAccessProfessionals] [IMPORTANT] Windows 10 update May 2020 is buggy
"I just read this newsletter from Woody Leonhard: https://www.askwoody.com/newsletter/free-edition-coming-to-a-pc-near-you-win10-2004-the-may-2020-update/
He strongly advises against installing the May 2020 update for Windows 10. Seems it;s loaded with bugs. So much so that MS isn't even pushing it out to its Surface machines yet.
I haven't upgraded to Win10 yet at home so I can't offer any personal insight."
The only trouble with the newer Windows is they do not allow you to choose when to update. They force it upon you.
Russ
Tidak ada komentar:
Posting Komentar