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

Just tested the OP's example databases. Neither crash for me in A365 version 2404 Beta Channel

For the record, my offending instr() function is wrapped in an iif() vs Where clause. Just as in-efficient - I am sure. Your reminder is well received.

Thanks for testing the sample DBs, Tom and Colin. Prompted by Colin's post testing with version 2404 I changed to the insider/beta channel and updated to the same version. It made no difference, I still get the crash with the post-C&R DB. I tried a new DB and made Table1 and Query1 from scratch, just in case it needed a clean start, but still crashes once you do C&R.

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-09T17:02:31+00:00

Just tested the OP's example databases. Neither crash for me in A365 version 2404 Beta Channel
Was this answer helpful?

0 comments No comments
Anonymous

2024-04-09T17:47:03+00:00

For the record, my offending instr() function is wrapped in an iif() vs Where clause. Just as in-efficient - I am sure. Your reminder is well received.
Was this answer helpful?

0 comments No comments
Anonymous

2024-04-09T17:48:01+00:00

Thanks for testing the sample DBs, Tom and Colin.

Prompted by Colin's post testing with version 2404 I changed to the insider/beta channel and updated to the same version.

It made no difference, I still get the crash with the post-C&R DB.

I tried a new DB and made Table1 and Query1 from scratch, just in case it needed a clean start, but still crashes once you do C&R.
Was this answer helpful?

0 comments No comments