• More problems with Windows patches breaking older Access databases

    Susan Bradley noted over the weekend that all of this month’s Windows patches break some Access 95-era Jet databases. That’s been acknowledged by Microsoft in all of the Knowledge Base articles.

    Now an anonymous poster here on AskWoody has raised the cry about a second kind of old-fashioned Access database problem. NSch_L gives the details on the Microsoft Answers forum:

    Problem with Access database after KB 4487017 [February’s Win10 version 1803 cumulative update] and KB 4487026 [this month’s Win10 1607/Server 2016 cumulative update]

    We use an Access 97 database for our applications as a master database, so we can easily destribute this to customers. We access this master database using Adox to get the tables and columns (fields), compare it to the live SQL database and make changes where necessary.

    Since the patch, we are getting errors when requesting the columns for wider tables. We are using an Adox.table and then use the .columns. When doing this for tables with more than 128 fields (exact number not sure) give error 3251 “Object or provider is not capable of performing requested operation”.

    This is causing all kinds of problems.

    It’s easy to click your teeth and tell these people that they should’ve upgraded their databases to a newer format about a hundred years ago. But it doesn’t work that way. Many of these older Access databases run drive key line-of-business apps that, for many reasons, can’t be changed without a complete re-write.

    That isn’t as… incompetent… as it sounds. Remember when Microsoft apparently lost the source code to the 32-bit Equation Editor, back in November 2017? People in glass houses, etc.