Oh what a tangled web Microsoft weaves …. a patch for Office has caused another bug in all versions of Access (365, 2019 back to 2010). The bug is the latest in a series of blunders for Office updates. It’ll take until next month for all customers to get a ‘patch of a patch of a fix’ but Microsoft has the gall to already mark their mistake as ‘fixed’.
The latest Access bug was caused by a buggy Office update which itself was supposed to fix a previous faulty patch for a security bug. In football this would be three ‘unforced errors’ in a row or three ‘own goals’ by the same player.
First we’ll explain the bug Microsoft added to Access and what you can do about it. Then we’ll look at the series of blunders from Microsoft over several months that led to this trouble.
After installing a 12 Nov 2019 patch for Office 365, 2019, 2016, 2013 or 2010, Access users start getting an error updating a query.
The query is wrongly marked as corrupt when it’s actually a bug from Microsoft. According to Microsoft, the error happens for an Update query that:
- Updates a single table (i.e. it updates a table, rather than the output of a Select query, or join)
- Specifies a WHERE clause (i.e. has entries in the Criteria row in the query designer)
That’s a pretty common situation. No wonder there have been complaints from Access customers around the world.
The latest bug happens after installing one of these 12 November 2019 patches.
The problem is also in Office 365 / Access 365.
More on these patches below.
According to Microsoft this problem is ‘fixed’. They make sure that’s in bold in the article about their mistake. But in the table below that boast, some customers are still waiting and some Access 2019 users will be waiting almost a month for Microsoft to repair its own mistake!
Source: Microsoft article about ‘Query is corrupt’ bug as at 20 Nov 2019
The problem isn’t ‘fixed’ until ALL Access users can get back to normal. Paying customers should not have to wait a month for a fix to a problem caused by Microsoft in the first place.
If you can’t wait for Microsoft, there is a workaround. The bug only occurs if you update a Table directly. Updating a Query is fine even if that Query just points to the table.
Microsoft offers this example code. This query triggers the bug:
UPDATE Table1 SET Table1.Field1 = "x" WHERE ([Table1].[Field2]=1);
Make a new Query that points to the entire Table.
e.g. ‘Query1’ is SELECT * from Table1;
Then change the original query to reference the new query not the table directly.
UPDATE Query1 SET Query1.Field1 = "x" WHERE ([Query1].[Field2]=1);
That will get your code working again. Of course, for many projects it’ll be a lot more complicated than this example.
How did this happen? – a chain of bad bug fixes
Amazingly, this bug in Access happened because of a faulty bug patch, for a previous faulty update, that itself fixed a bug caused by a security fix in Office.
In other words, Microsoft has caused a series of problems for their Office customers by not properly testing software patches, then making customers wait for months for fixes.
The Access query bug troubles started back in September (over two months ago) when all supported versions of Office got a security patch. Nothing new there, almost every month Microsoft has to fix some security lapse in their products.
- On 10 September 2019 Microsoft released a fix for Jet database security problem (Jet is the core database engine inside Access).
- That patch caused another bug to appear. Users got “File failed to upload” error when saving files to a network location.
- TWO months later, Microsoft finally fixed their second mistake. KB3085368 (12 Nov. 2019) fixed the ‘File failed to upload’ error they created in September.
- But that new ‘patch of a patch’ added the new ‘Query is corrupt’ as well!
- The timetable for fixing the ‘Query is corrupt’ bug are listed above.
If that wasn’t muddled enough, there’s more …
Another 12 November 2019 security update KB4484113 triggers both the ‘File failed to upload’ and the ‘Query is corrupt’ bugs!