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-05T19:21:14+00:00

    Can you roll back the update to verify whether that is, in fact, the cause of the new problem?

    Also, it looks like you installed 64 bit Office somewhere along the way. Did you modify all APIs in the accdb to be 64 bit compatible. That's a much more likely issue to cause problems like this.

    Was this answer helpful?

    0 comments
  2. Tom van Stiphout 40,216 Reputation points MVP Volunteer Moderator
    2024-04-05T19:19:58+00:00

    OK, at this point we do not have enough evidence that this is a regression related to the latest release to the Current Channel. At least 2 competent users have told me that they don't see this problem.

    It sounds much more likely your machine is in a bad state. You'll have to deal with that accordingly.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-04-05T18:38:26+00:00

    First grid line in my original post was blank, but that was just an artifact of the copy/paste. There are no records with empty or null values.

    Changed default printer to Microsoft Print to PDF. No help.

    ============

    Event Viewer info

    ============

    Faulting application name: MSACCESS.EXE, version: 16.0.17425.20146, time stamp: 0x66065ca3

    Faulting module name: ACEES.DLL, version: 0.0.0.0, time stamp: 0x65f145d4

    Exception code: 0xc0000005

    Fault offset: 0x0000000000030ba3

    Faulting process id: 0x0x5D4

    Faulting application start time: 0x0x1DA87896AE90119

    Faulting application path: C:\Program Files\Microsoft Office\root\Office16\MSACCESS.EXE

    Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Office16\ACEES.DLL

    Report Id: 1e0bde85-2394-40a7-9064-c5b36914be85

    Faulting package full name: 

    Faulting package-relative application ID: 

    ====================

    Fault bucket 1237486693595598140, type 4

    Event Name: APPCRASH

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: MSACCESS.EXE

    P2: 16.0.17425.20146

    P3: 66065ca3

    P4: ACEES.DLL

    P5: 0.0.0.0

    P6: 65f145d4

    P7: c0000005

    P8: 0000000000030ba3

    P9: 

    P10: 

    Attached files:

    \?\C:\Users\Reiff\Documents\Database-temptest.accdb

    \?\C:\Users\Reiff\AppData\Local\Temp{0185206A-62E4-4EEC-BB2E-A20B5CC1F2BC} - OProcSessId.dat

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d162f4fb-435f-425b-86c7-f6f815bc605b.tmp.WERInternalMetadata.xml

    WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20240404_1_EC_0_inject.etl

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c20756cc-f1f0-4f6c-8a03-75635da4cad9.tmp.etl

    WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.990427df-b8bc-476b-91c0-4b001412cfe4.tmp.etl

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.39044914-b076-448f-9dc1-aa34d63ba3ee.tmp.csv

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.fae7f984-fd38-4449-a3c2-26650d73cfa6.tmp.txt

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.69372383-0ef2-4f64-ae51-e9e120d89c58.tmp.xml

    These files may be available here:

    \?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MSACCESS.EXE_38d8eae31223a86237e3d4a7e528ab68cfc6e971_00000000_e9906e4f-3ce4-40d5-8ee2-ea2a16a6977e

    Analysis symbol: 

    Rechecking for solution: 0

    Report Id: 1e0bde85-2394-40a7-9064-c5b36914be85

    Report Status: 2147487744

    Hashed bucket: dcbdfaf4a7907994512c6f976209cd3c

    Cab Guid: 0

    Was this answer helpful?

    0 comments