Query is corrupt error message 11-14-2019

[Joe Y]

All of sudden, many vba functions in my Access application using query are not working with error message "Query is Corrupt".

Google results has one page from Microsoft dated 11/14/2019 referring the issue to a patch updates for MSI of several builds.

Does anyone know when MS will fix this issue? Will it be automatically repaired when fix is done by MS or is there some steps we need to do to fix the problem?

[DJRhino1175]

I was getting a lot of corruption issues awhile back and the only thing I could find that fixed my issues was a registry fix. I had to put it on every PC that uses access. I haven't had corruption since.

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
"FileInfoCacheLifetime"=dword:00000000
"FileNotFoundCacheLifetime"=dword:00000000
"DirectoryCacheLifetime"=dword:00000000

Save it in a .txt file as whatever name .reg

Hopefully that will work out for you.

You will probably have to fix your query to and any other objects that are not working in the database.

Good Luck

[cactusdata]

There is an official page on that issue:

Access error: "Query is corrupt"

[Joe Y]

The page from Microsoft I found from Google results is -

https://support.office.com/en-us/article/access-error-query-is-corrupt-fad205a5-9fd4-49f1-be83-f21636caedec

[Joe Y]

There is a workaround suggested by the support page. However, I have lots of VBA using query. Making each change is going to be a big challenge.

[Joe Y]

DJRhino1175,

I've never dealt with registry. Can you guide me through where to save the .reg file? Most of the users are using Windows 10 pro, some are Windows 7 Pro.

Thanks in advance!

[NeoPa]

Hi Joe.

Let's deal with this one point at a time :

1. I suspect that DJRhino's suggestion will not pertain to this issue. That is not to say, by any stretch of the imagination, that DJ wasn't being helpful and sharing his past experiences with you. Simply that his solution looks like it may be for another problem altogether.
2. I strongly recommend to you, and anyone that doesn't themselves have a good understanding of the Registry in Windows or how one can update it safely, that you don't go there. Every responsible web page ever written that includes instructions on such amendments always includes very strong warnings. If you aren't sure - don't go there.
3. The page you found on Google is exactly the same one that CactusData posted for you some four hours previously.
4. You may want to revisit that page. Everyone in the Access world seems to be suffering badly from this issue and everyone is talking about it. As you'd expect, those involved at MSFT, as well as many other prominent faces in the Access world that work in this area, are working very hard to get this resolved. The current version of the page gives various options - most of which depend on the version(s) of Access you're using.

5. Joe Y:
   Making each change is going to be a big challenge.

   It certainly is. Get your head around that and get on with it, is my best advice. You won't be unique in having to and there will certainly be help and support for all those, like yourself, who've been caught out by this issue.

As a last contribution, and though these are actually commercial sites and so normally unacceptable on Bytes.com, they are helpful in a very serious situation and are both by MVPs working closely with MSFT - the producer of the software, so I will include them :
Critical: Office Update breaks Access — Query is corrupt
Microsoft Access Query is Corrupt Error 3340

[NeoPa]

@DJRhino.

I believe that .REG files must actually be stored as UNICODE, rather than simple ASCII text as you'd normally find when creating a new document in most text editors. Many handle UNICODE if the file is already encoded that way - and of course for the most part they would look the same, but don't be confused into thinking they're standard ASCII text files.

I'm not pushing the use of .REG files you understand, just explaining a potential confusion in the hope that it may help.

The easiest way to create a workable .REG file is to select a part of the Registry tree within RegEdit.Exe and Export it from the Right-Click menu. That file will, necessarily, be encoded the right way for importing into a Registry tree at some other time.

NB. *** NEVER PLAY WITH THE REGISTRY ***
When you know enough to ignore this warning then you already know the dangers and that you hold full responsibility for all the results - intended & unintended.

[Joe Y]

Thanks for the advice. I’m working on the workaround suggested by Microsoft. Let’s hope they issue the fix soon.

[NeoPa]

I'm sorry I couldn't give you better news :-(

I strongly expect that a fix will come out very soon (Sorry - I really can't be more specific.), but I also believe that it's unlikely to be soon enough for most users to get away without having to handle this locally in one way or another.

Releasing a fix to the whole world for a problem that's only just been discovered is always going to be a gargantuan task. Timescales will never match user requirements in those situations.

I wish you the best of luck - of course - as I do everyone who's been affected by these patch releases.

[twinnyfo]

What a cluster! I guess I'll wait until November 24th.....

[NeoPa]

Hi guys.

This has been a very traumatic experience for everyone in the Access world but I can report that the Access Team in Redmond has been working extremely hard to get resolutions for the various supported versions still out there (Unsupported ones didn't suffer from the problem anyway ;-) ).

The following extracts are taken from emails from a member of the team :

Access:
Hi everyone,

We are getting patches out, this is the first available, for Office 2016 MSI installations:
November 18, 2019, update for Office 2016 (KB4484198)

Please let me know if you have any issues, or this doesn’t resolve the issue.
Just to be clear, this won’t help Office 2010 or 2013, for which patches will be following shortly.

For O365 Monthly Channel, or Office 2016 C2R installs, an update will be also be available very soon.

Followed very soon afterwards by :

Access:
Fixes for most everything, including O365, and 2016 C2R will be coming this week.

When the fix for O365/2016C2R are available, you will update using File/Account/Update Options/Update Now from within an Office application.
I'll send another note when new updates become available.

What may be more useful to many out there :

Access:
What’s not there (yet, but will be shortly), is that you can now download the update for O365 Monthly Channel/2016 C2R.
It should update you to 16.0.12130.2039 0.

So, you may be able to get the update before it's even notified publicly. It's in the works obviously.

[Joe Y]

Thanks for the update. Looking forward to all patches released. My users have various versions of Office installed.

[Rabbit]

Depending on how long it's going to take them to release the patch and how urgent your work is, it may be feasible to write a script to automate creating a view for all the tables and stepping through all the query definitions to point them to the views.