Instr() function crashes MS Access after 4/4/2024 update to office 16.0.17425.20146

Question

After Office updated to version 16.0.17425.20146 my MS Access crashes when running very simple functions. I created a new database with one table and one query.

Table1.Text1
Zebra
x-ray
4x4
Posted to X
Next
axe
None
extreme
wax

This works:

SELECT Table1.Text1, InStr(1,[Text1],"x") AS Field2

FROM Table1;

	Query1
Text1	Field2
Zebra	0
x-ray	1
4x4	2
Posted to X	11
Next	3
axe	2
None	0
extreme	2
wax	3

This crashes MS Access before returning any results:

SELECT Table1.Text1, InStr(1,[Text1],"x") AS Field2

FROM Table1

WHERE (((InStr(1,[Text1],"x"))>0));

I tried compact/repair. Tried recreating the database from scratch. Rebooted my computer. I uninstalled and re-installed MS Office.

Any ideas??

Answer 1

Hi,

The documenting article on AFo now has more information about the worarounds and the planned fix date by Microsoft.

Servus
Karl
****************
Access DevCon - online conference April 18+19
Access News
Access Forever
Access-Entwickler-Konferenz AEK

Answer 2

Hi,

I installed the new version 2404 which was published on May 1. In my tests the bug has been fixed.

Therefore, I've updated our documenting article on AFo with the fix information.

Servus
Karl
****************
Access Forever
Access News
Access DevCon
Access-Entwickler-Konferenz AEK

Answer 3

A reply to the documenting article on AFo has suggested that you could try adding the final optional, Compare, argument to Instr().

That actually worked, adding the optional param allowed the query to run without crashing Access.

I changed:

SELECT ID, Desc FROM Table1 WHERE InStr(Desc, ".") > 0;

to:

SELECT ID, Desc FROM Table1 WHERE InStr(1,Desc, ".", 1) > 0;

This is a helpful temp fix while MS sort out the underlying issue.

Thanks GroverParkGeorge for the info.

Answer 4

HERE IS A WORK-AROUND

From the event viewer crash data, the error appears to be in ACEES.DLL. I replaced my 4/8/2024 copy of this file with one I pulled from another PC where ACEES.DLL has a modified date of 3/8/2024. The InStr() crash does not happen anymore!

More specifically, in folder

C:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX64\Microsoft Shared\Office16

I renamed the newer (buggy) version:

and copied this older version into the same folder

Problem solved, at least for now.

Maybe the admins can post a copy of the older DLL for others to download. I'd do it myself, but I expect the moderators would (should!) take it down.

From the lack of complaints, I surmise that this is not a widespread issue. I'm content with the work-around for now, and leave it with the MS team to decide if fixing the bug is worth their time.

Thank you all!

Answer 5

Are you able to post a stripped down version of your database that reproduces the error with InStr on your machine? I can try running your database on my machine with 64-bit Access if you upload a sample. Or, try changing to the more stable (in my opinion) Semi-Annual Enterprise Channel. If there is something honked up in a library file it may get replaced in the process.

I just checked and Microsoft reports for my Semi-Annual Enterprise Channel I am up-to-date. So, even though my version number is somewhat lower, it appears as if I cannot get the same exact version as you to test. I'd likely have to change the update channel to "Current", which I am not willing to do. I prefer the stability of letting others thoroughly test releases before they are made available to me!