MS Access crashes when filtering a table or SELECT query

Anonymous
2020-01-21T18:57:16+00:00

Since about 1/20/2020, my MS Access software (from my Office 365 edition/Windows 10) will crash when I try to filter a database table or filter the results from a SELECT query.  This hasn't been a problem previously. 

Version 1912 (Build 12325.20298)

Anyone else experiencing this problem?

Microsoft 365 and Office | Access | For home | 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

47 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-01-27T20:15:02+00:00

    Firstly, if you are running V1912, you must be using the Insider Channel or Monthly, both of which are to absolutely be avoided at all cost for any production PC!!!   Microsoft is simply pushing out too many bugs, one after another, to be using those update channels.

    I don't have the issue, simply trying to help other recover from such issues, and the normal troubleshooting is:

    • Compact and repair - try again
    • Compile and make sure there are no error and all references are ok - try again
    • Decompile, Compact and Repair, Compile, Compact and Repair - try again
    • Create a new blank db, import everything - try again
    • Perform and Office Repair - try again
    • Try Updating or Reverting to other builds - try again
    • Uninstall, Reinstall - try again

    So what I'm suggesting is normal Access/IT troubleshooting.  If your IT hasn't done so, you should mention it to them, point them to this thread.  But realistically, with the non-stop bugs out of Microsoft Updating and Reverting builds is now become a normal requirement to keep things operational.  Then again, they shouldn't have you using the Monthly Update channel in the first place!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-01-27T19:33:24+00:00

    Have you tried reverting back to 1911, 1910, 1909, ...?

    No, I am on a company machine. Unless that is a fix IT comes up with there will be no version changes.

    Did you roll yours back and if so did it fix it?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-01-27T19:13:32+00:00

    Have you tried reverting back to 1911, 1910, 1909, ...?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-01-26T15:36:58+00:00

    Had done that procedure before but did it again.  Seemed to help until this morning - CRASH  - main problem shows "MS ACCESS Exception Code c0000005"

    -potential memory issue - did memory check - no problems found-

    Will uninstall/reinstall Access when I get a chance.

    I think Microsoft has caused a problem with this months Office update just like they did a few weeks back when everything was crashing until the fessed up and sent out a special fix

    Recent build 12325.20288 is suspect based on when issue started.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-01-21T21:09:42+00:00

    Also, if your backend is SQL Server, then perhaps the issue relates to

    https://www.devhut.net/2020/01/17/access-bug-sql-server-identity-bug-with-access/

    Was this answer helpful?

    0 comments