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. Anonymous
    2024-04-11T13:53:37+00:00

    Hi Reiff, (and other people who used this workaround)

    We have now published a documenting article on AFo. We also discussed your DLL change workaround. Are you only using it out of technical interest or do you have a real technical or organizational use case and reason for doing so? Because you can't switch to an older build or slower channel or whatever?

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

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-04-11T13:44:35+00:00

    I wonder if this is in anyway related to a very similar issue I had a number of years ago.
    Discussion here

    https://www.access-programmers.co.uk/forums/threads/nested-instr-issues.317649/page-3

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-04-11T08:33:12+00:00

    I was just executing a query. I cannot try anymore because I switched to Microsoft 365 Semi Annual Enterprise channel and the problem is gone now.

    Microsoft® Access® for Microsoft 365 MSO (Version 2403 Build 16.0.17425.20176) 64-bit

    -> had mentioned issues

    Microsoft® Access® for Microsoft 365 MSO (Version 2308 Build 16.0.16731.20542) 64-bit

    -> no issues, version I have now

    What I find really odd is that a new database created in Safe Mode did not have the problem, and a new blank database in "normal" mode had the problem. I don't get why a new blank database should be created diferent in safe vs normal mode.

    Was this answer helpful?

    0 comments