Share via

Strange errors in Access

Anonymous
2019-11-24T12:28:59+00:00

I have developed an Access database for use by a friend. I developed it using Access 2013.

My friend is using Access from Office 365. Everything has been fine for many months.

Now, when either of us goes to use the database it gives unexpected error messages.

One of these says Run-time error '3340': and on the next line Query '' is corrupt.

Digging further, I have found that this error happens whenever I try to run an Update query with a where clause.

I have now created a blank database and manually created a simple table. This error still persists. The query works fine without the whereclause. Similarly, the same query made into a Select query with a where clause also works fine.

What the???

My original database had normally been updated on my computer (2013) and then used on my friend's. I think the problems began when I took an updated version from him (365) and brought it back to my computer. But that doesn't explain why update queries now have a problem in any database.

Kind regards

Alan P

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Anonymous
    2019-11-24T12:52:34+00:00

    Well, this is but the latest bug caused by a series of flawed security updates that were released November 12th:

    *Access 2010 – **KB4484127**Access 2013 – **KB4484119*Access 2016+ – KB4484113 Access 2016+ – KB3085368

    You can read about the entire blunder by reviewing

    https://www.devhut.net/2019/11/14/access-bug-error-3340-query-is-corrupt/

    The article includes various workaround and fixes (for certain versions of Access).

    The good news is that if you are running Access 2016, 2019 or Access 365, fixes are now available you need only update.

    The bad news is that if you are running 2010 or 2013 you are stuck with one of the options:

    Was this answer helpful?

    0 comments No comments