[AccessD] [dba-SQLServer] DSN Tables - Could not find installable ISAM

[Mark Simms]

Based on recent experience with updates, for critical applications that are based on Office 365 (Excel, Access, etc) I have recommended that Automatic Updates be turned off.
There are other opinions who say this strategy will keep critical security updates from getting installed.

Mark Simms
marksimms at verizon.net


-----Original Message-----
From: Gustav Brock via AccessD <accessd at databaseadvisors.com>
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Cc: Gustav Brock <gustav at cactus.dk>
Sent: Fri, Dec 20, 2019 3:23 am
Subject: Re: [AccessD] [dba-SQLServer] DSN Tables - Could not find installable ISAM

Hi David

Version 1912 is the Insiders Release (sometimes called Monthly-Targeted), so only people getting pre-release builds would see this.
Version 1911 is still the Monthly Channel build. It doesn’t have this issue.

The issue has been fixed, and an update is available (now), just do the File/UpdateOptions/UpdateNow, and you should get build 16.0.12325.20214 which has the fix. 
Over the next week or so, it will automatically update if you don’t force it, but it is available to everyone now.

If you don't want such happenings and surprises, don't run the Insiders Release. As the name implies, it is intended for developers and first-movers who are prepared for this and that. Don't run it at normal users.
 
/gustav

-----Oprindelig meddelelse-----
Fra: AccessD <accessd-bounces at databaseadvisors.com> På vegne af David McAfee
Sendt: 19. december 2019 19:25
Til: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Emne: Re: [AccessD] [dba-SQLServer] DSN Tables - Could not find installable ISAM

Probably not related, but Microsoft put out another bad update this week that broke existing apps on our end (2nd bad update in 3 weeks!)

All of the sudden we were experiencing ODBC call failed and/or invalid cursor state errors.

I reverted our O365  boxes with version 1912 (build 12325-20172) to 1911 (build 12228.20364) and the odbc errors went away.

Once again, might not be your issue, but I'd hate to be troubleshooting an odbc issue, going nuts, only to find out it was due to a bad ms update!
Grrrr!!!

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com