Access randomly crashing when I try to filter

Anonymous
2024-06-05T15:25:06+00:00

Having this issue for the past few days.
Every once in a while, when I try to filter a field, access will crash. It doesn't matter how big the table I'm trying to filter is.

Sometimes it crashes when I'm not even touching it. It's just open in the background when I'm working on something else.
More rare though. So not sure if it's even related.

Any ideas?

Microsoft 365 and Office | Access | For home | Other

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 No comments

53 answers

Sort by: Most helpful
  1. Anonymous
    2024-08-11T21:04:48+00:00

    Hi,

    Kathrin's repro file and steps "worked" for me to reliably generate the crash. So I have forwarded it to the Access team at Microsoft. With a repro file and 3 Windows crash reports they should be well equipped. ;-)

    We will keep the bug status up to date in our documenting AFo article and also inform you here when there is important news.

    Servus
    Karl
    ****************
    Access News, Forever, DevCon
    Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-08-11T17:11:44+00:00

    Hi Kathrin,

    You can use the email address that you find at the end of the text on this page.

    Please change the email subject and include the information about the Windows and Office version+build where the crashes happen reliably for you.

    Servus
    Karl
    ****************
    Access News, Forever, DevCon
    Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-08-11T16:35:05+00:00

    Hi Judy,

    It depends somewhat on the factors that play a role in this problem.

    Maybe a video that you upload somewhere might help if it shows relevant details.

    Another would be a step-by-step guide with the technical details such as Office and Windows version+build and possibly a Windows crash report.

    Ideally, there would be a small reliably crashing example file. Of course, this only works if special requirements within the database play a role and the environment is not solely responsible for the crashes.

    Servus
    Karl
    ****************
    Access News, Forever, DevCon
    Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

    Moin Karl,

    I have the same problem on some PCs and my "users" get angry more and more.

    Now I've created a new empty database and imported one table and one form from my application.

    With this I've reproduced the crash reliably.

    Do you have an email address for me so that I can send you the data and some more info including a screenshot of the steps?

    Gruß, Kathrin

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-08-11T01:14:04+00:00

    Source:        Application Error

    Date:          8/10/2024 9:06:17 PM

    Event ID:      1000

    Task Category: Application Crashing Events

    Level:         Error

    Keywords:     

    User:          CENTRAL\jcohen2

    Computer:      wvdNdsk1-2b6e.central.nyced.org

    Description:

    Faulting application name: MSACCESS.EXE, version: 16.0.17830.20138, time stamp: 0x66aab148

    Faulting module name: MSACCESS.EXE, version: 16.0.17830.20138, time stamp: 0x66aab148

    Exception code: 0xc0000005

    Fault offset: 0x000000000081844f

    Faulting process id: 0x0x28054

    Faulting application start time: 0x0x1DAEB8A79CB39F5

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

    Faulting module path: C:\Program Files\Microsoft Office\Root\Office16\MSACCESS.EXE

    Report Id: 63c9ad5b-72a3-4573-89df-f6a617e0619b

    Faulting package full name:

    Faulting package-relative application ID:

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />

        <EventID>1000</EventID>

        <Version>0</Version>

        <Level>2</Level>

        <Task>100</Task>

        <Opcode>0</Opcode>

        <Keywords>0x8000000000000000</Keywords>

        <TimeCreated SystemTime="2024-08-11T01:06:17.9425596Z" />

        <EventRecordID>26146</EventRecordID>

        <Correlation />

        <Execution ProcessID="156416" ThreadID="65544" />

        <Channel>Application</Channel>

        <Computer>wvdNdsk1-2b6e.central.nyced.org</Computer>

        <Security UserID="S-1-5-21-756204042-1246811783-1072919933-129047" />

      </System>

      <EventData>

        <Data Name="AppName">MSACCESS.EXE</Data>

        <Data Name="AppVersion">16.0.17830.20138</Data>

        <Data Name="AppTimeStamp">66aab148</Data>

        <Data Name="ModuleName">MSACCESS.EXE</Data>

        <Data Name="ModuleVersion">16.0.17830.20138</Data>

        <Data Name="ModuleTimeStamp">66aab148</Data>

        <Data Name="ExceptionCode">c0000005</Data>

        <Data Name="FaultingOffset">000000000081844f</Data>

        <Data Name="ProcessId">0x28054</Data>

        <Data Name="ProcessCreationTime">0x1daeb8a79cb39f5</Data>

        <Data Name="AppPath">C:\Program Files\Microsoft Office\Root\Office16\MSACCESS.EXE</Data>

        <Data Name="ModulePath">C:\Program Files\Microsoft Office\Root\Office16\MSACCESS.EXE</Data>

        <Data Name="IntegratorReportId">63c9ad5b-72a3-4573-89df-f6a617e0619b</Data>

        <Data Name="PackageFullName">

        </Data>

        <Data Name="PackageRelativeAppId">

        </Data>

      </EventData>

    </Event>

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-08-10T14:10:52+00:00

    Hi Mark,

    I’m not a windows debugger. You will have to direct me as to what specific information, reports or log files you need.

    To get the Windows log text with the crash information:

    1. press <Win>+<X>
    2. in the menu select Event Viewer
    3. in the viewer go to Windows Logs - Application and search for an Error entry with the right time
    4. When you double click on the entry you get a dialog with a Copy button. If it's an Access crash the text looks similar to this example. The language depends on your Windows settings but the essential XML text isn't localized. This information can be helpful for the Microsoft engineers.

    Servus
    Karl
    ****************
    Access Forever News DevCon
    Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

    Was this answer helpful?

    0 comments No comments