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: Oldest
Most helpful Newest Oldest
  1. 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
  2. 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
  3. Anonymous
    2024-04-09T15:50:58+00:00

    dbMonkey:

    > Just running C&R on this new tiny simple DB resulted in it starting to crash when doing the filter test, where it worked fine on the freshly created DB before C&R was run.

    Just curious....have you tried any other functions such as Left (or Left$), Mid (or Mid$), etc.?
    If this issue is reproducible for folks on the Access team at Microsoft, after a compact & repair as you stated, then I will say you've done very good documentation of the problem. The big question is if it is reproducible for others.

    I just tried your samples using my 64-bit MS Access, which is the Semi-Annual Enterprise Channel version [Version 2308 (Build 16731.20600 Click-to-Run). Both versions work fine, including after compact and repair. Interestingly, my compacted sizes are a bit smaller than the sizes you posted to your public OneDrive folder. Not sure if that means anything...

    Was this answer helpful?

    0 comments