none
Corrupt query Question RRS feed

  • Question

  • I have a access 2013 query as illustrated below.

    UPDATE Reject_Information_TBL SET Reject_Information_TBL.Suplier = "N/A"
    WHERE (((Reject_Information_TBL.Suplier) Is Null));

    I realize suplier is spelled wrong, but this query yields the following error.

    Any Ideas?

    Interestingly enough, the query below yields a similar error.

    UPDATE Approval_Log SET Approval_Log.Date_Difference = Null
    WHERE (((Approval_Log.Date_Recieved) Is Not Null));

    • Edited by tkosel Wednesday, November 20, 2019 11:49 PM
    Wednesday, November 20, 2019 11:11 PM

Answers

  • It's only the latest, of many, bugs introduced by a series of flawed security updates that were released Nov 12th.

    Depending on the version of Access you have installed, there are 4 updates causing this issue:

    Access 2010 – Uninstall update KB4484127
    Access 2013 – Uninstall update KB4484119
    Access 2016 – Uninstall update KB4484113
    Access 2016 – uninstall update KB3085368

    You can learn about all the details of this entire issue at https://www.devhut.net/2019/11/14/access-bug-error-3340-query-is-corrupt/ including workarounds.

    Daniel Pineault, 2010-2019 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net

    • Marked as answer by tkosel Thursday, November 21, 2019 9:58 PM
    Thursday, November 21, 2019 2:07 AM
  • That looks OK (assuming that Suplier is a text field). Have you tried it?

    Regards, Hans Vogelaar (http://www.eileenslounge.com)

    • Marked as answer by tkosel Thursday, November 21, 2019 9:58 PM
    Thursday, November 21, 2019 3:38 PM
  • Daniel,

    as usual, thanks for your prompt and knowledgeable response.  I tried to uninstall KB4484119 for access 2013 which I am using, but couldn't figure out how to do it.  It wasn't on any lists, or I couldn't find it.

    While I don't want to do this, I think I will try the workaround.  Can you check my syntax?

    First Query should be:

    Select * from Reject_Information_TBL;   (I will call this NewQuery)

    Original Query Should be changed to:

    UPDATE NewQuery SET NewQuery.Suplier = "N/A"
    WHERE (((NewQuery.Suplier) Is Null));

    Does that seem correct to you?

    • Marked as answer by tkosel Thursday, November 21, 2019 9:58 PM
    Thursday, November 21, 2019 2:49 PM

All replies

  • It's only the latest, of many, bugs introduced by a series of flawed security updates that were released Nov 12th.

    Depending on the version of Access you have installed, there are 4 updates causing this issue:

    Access 2010 – Uninstall update KB4484127
    Access 2013 – Uninstall update KB4484119
    Access 2016 – Uninstall update KB4484113
    Access 2016 – uninstall update KB3085368

    You can learn about all the details of this entire issue at https://www.devhut.net/2019/11/14/access-bug-error-3340-query-is-corrupt/ including workarounds.

    Daniel Pineault, 2010-2019 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net

    • Marked as answer by tkosel Thursday, November 21, 2019 9:58 PM
    Thursday, November 21, 2019 2:07 AM
  • Daniel,

    as usual, thanks for your prompt and knowledgeable response.  I tried to uninstall KB4484119 for access 2013 which I am using, but couldn't figure out how to do it.  It wasn't on any lists, or I couldn't find it.

    While I don't want to do this, I think I will try the workaround.  Can you check my syntax?

    First Query should be:

    Select * from Reject_Information_TBL;   (I will call this NewQuery)

    Original Query Should be changed to:

    UPDATE NewQuery SET NewQuery.Suplier = "N/A"
    WHERE (((NewQuery.Suplier) Is Null));

    Does that seem correct to you?

    • Marked as answer by tkosel Thursday, November 21, 2019 9:58 PM
    Thursday, November 21, 2019 2:49 PM
  • That looks OK (assuming that Suplier is a text field). Have you tried it?

    Regards, Hans Vogelaar (http://www.eileenslounge.com)

    • Marked as answer by tkosel Thursday, November 21, 2019 9:58 PM
    Thursday, November 21, 2019 3:38 PM
  • Hans and Daniel,

    I tried it, and it solved the problem.  It would appear that I have to do this for every update query right?  I imagine that microsoft will reimburse me for my trouble eventually right?

    Thanks again for all your help!

    Thursday, November 21, 2019 9:58 PM
  • A fix for Access 2013 should be released tomorrow (November 22, 2019). See https://support.office.com/en-us/article/access-error-query-is-corrupt-fad205a5-9fd4-49f1-be83-f21636caedec

    Regards, Hans Vogelaar (http://www.eileenslounge.com)


    Thursday, November 21, 2019 10:10 PM
  • That link shows release date for Access 2013 fix now pushed back to November 29 or December 10 depending on whether you have MSI or click to run installation.  Sigh.

    -Bruce


    Friday, November 22, 2019 5:34 PM
  • Hi Daniel,

    I use Access daily  for my 24/7 business and have just encountered this problem today. I don't recall installing any updates. I am not technical. And now I cannot produce any management accounts. Can you help?

    Thank

    Bhavesh

    Saturday, November 23, 2019 10:03 AM
  • If you have the installer (MSI) version of Access 2013, a fix is now available:

    https://support.microsoft.com/en-us/help/2965317/november-27-2019-update-for-office-2013-kb2965317


    Regards, Hans Vogelaar (http://www.eileenslounge.com)

    Wednesday, November 27, 2019 7:34 PM
  • It was probably installed automatically by Windows Update.

    For us to be able to help you, you'd need to tell us what version of Access you are using, if it is MSI, store or C2R and the build number.  With all of this, we will be able to tell you exactly how to address the issue.


    Daniel Pineault, 2010-2019 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net

    Wednesday, November 27, 2019 8:25 PM
  • Hans,

    Thanks for the information.  Unfortunately I have a "Click to Run" (C2R) version, not the MSI version.  I guess I will have to continue to be patient.



    • Edited by tkosel Wednesday, November 27, 2019 9:57 PM
    Wednesday, November 27, 2019 8:34 PM