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??

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!

I tried to open the accdb in Access 2019, 64 bit. Query2 --the one designated as not working--crashed Access once, and but then opened correctly on subsequent attempts. Then my VM itself crashed, so I am going to have to start over. I hope I don't have to recreate the VM, what a PITA that would be. It appears there may well be some problem here, but my testing is not consistent enough to know what that would be yet.

>>Query2 --the one designated as not working--crashed Access once, and but then opened correctly on subsequent attempts. Then my VM itself crashed<< ****! That sucks. Something definitely wrong with that DLL. Even so, no component of Office should crash a VM like that.

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

Anonymous

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??

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

Answer accepted by question author

Anonymous

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

0 comments

Answer accepted by question author

Anonymous

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

0 comments

54 additional answers

Anonymous

2024-04-08T14:18:49+00:00

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!
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
George Hepworth 23,120 Reputation points Volunteer Moderator

2024-04-08T14:36:58+00:00

I tried to open the accdb in Access 2019, 64 bit. Query2 --the one designated as not working--crashed Access once, and but then opened correctly on subsequent attempts. Then my VM itself crashed, so I am going to have to start over. I hope I don't have to recreate the VM, what a PITA that would be.

It appears there may well be some problem here, but my testing is not consistent enough to know what that would be yet.
Was this answer helpful?

0 comments No comments
Anonymous

2024-04-08T15:48:24+00:00

>>Query2 --the one designated as not working--crashed Access once, and but then opened correctly on subsequent attempts. Then my VM itself crashed<<

****! That sucks. Something definitely wrong with that DLL. Even so, no component of Office should crash a VM like that.
Was this answer helpful?

0 comments No comments