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

Yes, VBA compile without any errors

No, I didn't. I've installed the 64-bit version since last year, and everything worked fine until today. Weirdly, the machine using the Access 32-bit version runs the same front end and the same Office version without error

Are you able to post a stripped down version of your database that reproduces the error with InStr on your machine? I can try running your database on my machine with 64-bit Access if you upload a sample. Or, try changing to the more stable (in my opinion) Semi-Annual Enterprise Channel. If there is something honked up in a library file it may get replaced in the process. I just checked and Microsoft reports for my Semi-Annual Enterprise Channel I am up-to-date. So, even though my version number is somewhat lower, it appears as if I cannot get the same exact version as you to test. I'd likely have to change the update channel to "Current", which I am not willing to do. I prefer the stability of letting others thoroughly test releases before they are made available to me!

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-08T03:36:31+00:00

Yes, VBA compile without any errors
Was this answer helpful?

0 comments No comments
Anonymous

2024-04-08T03:43:01+00:00

No, I didn't. I've installed the 64-bit version since last year, and everything worked fine until today. Weirdly, the machine using the Access 32-bit version runs the same front end and the same Office version without error
Was this answer helpful?

0 comments No comments
Anonymous

2024-04-08T07:11:56+00:00

Are you able to post a stripped down version of your database that reproduces the error with InStr on your machine? I can try running your database on my machine with 64-bit Access if you upload a sample. Or, try changing to the more stable (in my opinion) Semi-Annual Enterprise Channel. If there is something honked up in a library file it may get replaced in the process.

I just checked and Microsoft reports for my Semi-Annual Enterprise Channel I am up-to-date. So, even though my version number is somewhat lower, it appears as if I cannot get the same exact version as you to test. I'd likely have to change the update channel to "Current", which I am not willing to do. I prefer the stability of letting others thoroughly test releases before they are made available to me!
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments