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

54 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. George Hepworth 23,120 Reputation points Volunteer Moderator
    2024-04-08T21:43:47+00:00

    "...it only crashes when the source database is in a Box.com or Dropbox folder."

    Is this the case? Can you verify that the same accdb placed in one of those locations always crashes, but not when placed in a local folder?

    It's pretty widely understood that it's not a good idea to open accdbs in OneDrive, Dropbox, etc, albeit for other reasons.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-04-08T20:52:46+00:00

    >>Don't assume that the ACEES.DLL file on George's VM was involved with the crash on his machine <<

    Agreed. My statement was more an expression of sympathy than an attempt at diagnosis.

    I see how my statement, " . . no component of Office should crash a VM . . . " could be taken as me assuming that it DID crash the VM. Quite the opposite, I was intending to state that no Office component should be able to crash a VM, so it probably didn't.

    Thanks for all your help on this problem. I appreciate all the time and effort that you and the other forum experts put into helping the rest of us.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-04-08T20:40:50+00:00

    Thanks for all your input. I don't think it was a download-related corruption of that file. It broke when Office was auto-updated. Then I uninstalled Office and reinstalled from the click-to-run online installer. Same problem. Then I uninstalled Office, rebooted, and downloaded the offline installer. Had the same problem. The likelihood of 3 identical corruptions using 3 different installation methods seems remote. I'm more likely to think it's some specific combination of elements on my machine. Maybe that version of the DLL has an incompatibility with a specific version of .NET; or it only crashes when the source database is in a Box.com or Dropbox folder. Or my specific malware defenses are killing a process due to a false positive detection.

    I'm willing to provide relevant information to anyone who wants to dig into the problem.

    Was this answer helpful?

    0 comments