They make sure that’s in bold in the article about their mistake. The problem is also in Office 365 / Access 365.Īccording to Microsoft this problem is ‘fixed’. The latest bug happens after installing one of these 12 November 2019 patches. No wonder there have been complaints from Access customers around the world. has entries in the Criteria row in the query designer) it updates a table, rather than the output of a Select query, or join) According to Microsoft, the error happens for an Update query that: The query is wrongly marked as corrupt when it’s actually a bug from Microsoft. See: Why upd ating Office is like the Kobayashi Maru a ‘no win scenario’ The bugĪfter installing a patch for Office 365, 2019, 2016, 2013 or 2010, Access users start getting an error updating a query. Then we’ll look at the series of blunders from Microsoft over several months that led to this trouble. In football this would be three ‘unforced errors’ in a row or three ‘own goals’ by the same player.įirst we’ll explain the bug Microsoft added to Access and what you can do about it. 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. 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 bug is the latest in a series of blunders for Office updates. a patch for Office has caused another bug in all versions of Access (365, 2019 back to 2010). Oh what a tangled web Microsoft weaves ….
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |