A family of Microsoft relational database management systems designed for ease of use.
Do you use many fields in your tables? ..i am thinking that might you are pulling some queries that go beyond the limit of 255 per table..or something similar.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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?
A family of Microsoft relational database management systems designed for ease of use.
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.
Do you use many fields in your tables? ..i am thinking that might you are pulling some queries that go beyond the limit of 255 per table..or something similar.
I'd try, as a test, to revert to 1911, 1910, 1909 just to see. Then you'd know for sure if it was 1912 or not. From there, well, you'd have to make a choice as to what to do.
Just rolled user back to Version 1911 (Build 12228.20364) I will keep you posted as it will take time to test. User says it seem to work fine when she first boots up and then after time it crashes likes its a memory build up or leak. She thinks maybe its related to the clipboard but these are all wild guesses. We will have to see what this 1911 build does for her.
I'd try, as a test, to revert to 1911, 1910, 1909 just to see. Then you'd know for sure if it was 1912 or not. From there, well, you'd have to make a choice as to what to do.
Have you tried reverting back to 1911, 1910, 1909, ...?
We tried reverting back from the latest Version 1912 (Build 12325.20298) to Version 1912 (Build 12325.20288) IT worked for half a day then same issue, We are worried about trying a later version cause of other issues they had.
I have a db that's only used for browsing Sql Server tables, no code. It exhibits the same behavior.
Last occurrence:
Log Name: Application
Source: Application Error
Date: 1/25/2020 12:10:48 PM
Event ID: 1000
...
Description:
Faulting application name: MSACCESS.EXE, version: 16.0.12325.20298, time stamp: 0x5e169778
Faulting module name: MSACCESS.EXE, version: 16.0.12325.20298, time stamp: 0x5e169778
Exception code: 0xc0000005
Fault offset: 0x0049787b