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

Anonymous
2024-04-05T16:32:38+00:00

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

Microsoft 365 and Office | Access | For business | 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

54 additional answers

Sort by: Most helpful
  1. Anonymous
    2024-04-09T15:40:42+00:00

    Thanks GPG,

    I'll monitor this topic and help with any testing that is needed.

    Was this answer helpful?

    0 comments No comments
  2. George Hepworth 23,120 Reputation points Volunteer Moderator
    2024-04-09T14:14:43+00:00

    I've renewed the request for the Access team to investigate this problem.

    Thanks for your persistence, and for the extensive testing all of you have done.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-04-09T13:28:40+00:00

    I took some time and tested those scenarios. Crash still happens even when database file is not in OneDrive, Dropbox, or Box.com folders. It also happens when 3rd-party anti-malware protection is disabled.

    I agree with the recommendation to avoid placing shared database files on cloud services.

    A note for those using my work-around that uses an old version of ACEES.DLL . . . the MS Office automated update procedure "fixed" my ACEES.DLL overnight. I had to manually re-replace it with the old version.

    Was this answer helpful?

    0 comments No comments