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-13T12:31:02+00:00

    Karl, that's great, thank you very much! I've just informed my users and will keep you up to date about their feedback.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-08-13T11:22:23+00:00

    Thank you Karl! That's fantastic!!!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-08-13T11:16:00+00:00

    Hi,

    If you are in the Current Channel, you should receive version 2407 build 17830.20166 with a fix for the problem in the course of the day. To get it immediately, you can press Update Now in the update options of the Account page.

    In my tests, the crashes no longer occurred with this build and that should be the case with any build >=16.0.17830.20056. Please let us know if it works for you and especially if not.

    edit: BTW you don't even need the latest build, because version 2407 build 17830.20138 from Aug 1 should still receive the fix today. A restart of Access should be sufficient there.

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

    Was this answer helpful?

    0 comments No comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  5. Anonymous
    2024-08-12T23:32:39+00:00

    Thanks Karl much appreciated. I have rolled 365 back to an older version and it is working fine now :-)

    Was this answer helpful?

    0 comments No comments