Forum Discussion
Run-time Error '3340'
I am having trouble with access. I use it every day and need it to work. please help me.
13 Replies
- This was affecting me at work as well with 2016 and 2019 versions of Access where there wasn't an update I could simply uninstall to temporarily fix the issue. Today I successfully did a System Restore from the Windows Recovery options back to a week ago before the update was installed and Access is good to go again. In Access > Account I also disabled updates so I hope that it will stay good.
JonathynYes, this the erroneous Query is Corrupt message caused by the Security Update Microsoft released last week. My team wrote a paper that describes the problem in more detail, the causes, Microsoft responses and workarounds you can make now:
http://fmsinc.com/MicrosoftAccess/Errors/query_is_corrupt/
Hope this helps.
I have this Access error. I have Office 365 and I have followed the suggestion to update my Office version within Access. I have done this and now have version 1910 Build 12130.20410 Click-to-Run. This is the latest update. The error still persists. Please help !!!
CaptainTall45 I had the same issue crop up
The problem code was a docmd.runsql "Update Table Set field1 = #" & now() & "# Where ID = " & str(intID)
I changed it to
dim wrst as recordset
set wrst = currentdb.openrecordset("SELECT * FROM Table WHERE ID = " & str(intID))
if not wrst.eof then
wrst.edit
wrst("field1") = now()
wrst.update
end if
wrst.close
I found that the uninstall previous updates doesn't work with Office 365 and that the only thing I found is to use the deployment tool to set back to a prior version.
Not something I wanted MANY end users who are not all computer saavy to have to walk through so I did some digging.
We have (primarily) one tool utilizing MS Access which has this error. I don't get it on my machine because I have a surface, and because I cannot update the drive to a larger one I use an sd card for my user folder which does not allow the major upgrades to run. However I found a laptop which had the error. I ran the tool and went into debug to find where the offending query was.
It utilized a Update Filename SET field = '0' WHERE nz(field,'')='';
I changed it to eliminate the WHERE statement and it worked.
Update Filename SET field = nz(field,'0');
sure, technically it is Updating each record (I am told) but I have noticed no significant performance hit.
My thought is maybe this is only a problem when WHERE is utilized?
- can I chat with anyone to fix this error
Jonathyn Is just a problematic Update that caused havoc
You have to uninstall these Updates to have it resolved
Access 2010 – Uninstall update https://support.microsoft.com/en-ca/help/4484127/security-update-for-office-2010-november-12-2019
Access 2013 – Uninstall update https://support.microsoft.com/en-ca/help/4484119/security-update-for-office-2013-november-12-2019
Access 2016 – Uninstall update https://support.microsoft.com/en-ca/help/4484113/security-update-for-office-2016-november-12-2019And recently added to the list
Access 2016 – uninstall update https://support.microsoft.com/en-ca/help/3085368/november-12-2019-update-for-office-2016-kb3085368
- is there any answer to this problem
