Access crashes since latest (June) Office 365 update 16.0.12827.20268

Anonymous
2020-06-08T08:51:19+00:00

Since the latest Office 365 Update (June update) a returning error emerges when opening (larger) forms in MSACCESS.

Using the Access runtime (2013 tested on) instead of the full Office365 Access seems to solve this problem for now.

Here is a summary of the error, below I added a screenshot of the event viewer error log (it is in dutch though):

Faulting application name: MSACCESS>EXE, version: 16.0.12827.20268

Faulting module name: ntdll.dll, version: 10.0.18362.815

Exception code: 0xc0000374

Fault offset: 0x000dfa1d

Faulting process id: 0x1f30

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
Answer accepted by question author
Anonymous
2020-06-09T03:27:13+00:00

Thank you for your feedback. Very soon, we will ship a new data type, known as Date & Time Extended, which enhances syntax compatibility with SQL while increasing accuracy & level of detail in date & time records.

While the feature is not yet enabled in Current Channel builds, most of the code for the feature is in the product in an inactive state. Nonetheless, we are aware of a problem that currently exists with this new code. As of today, if you are on version 2005, build 12827.20010 or greater, and you manipulate Decimal fields (Access DataType=Number/FieldSize=Decimal, or SQL DataType=Decimal) using DAO (Data Access Objects), you might have identified your app crashing. If you hover a variable with the type in VBA code, you may see that the field is not being displayed properly; either reading as ‘?????’ or giving a Type Mismatch error, or Access may crash.

We are very sorry for the inconvenience this causes in your Access app. The Access team is working on resolving this issue as soon as possible, and we will report back to you once this error has been fixed. In the interim, we’d recommend for you to roll back to a previous version (https://support.microsoft.com/en-us/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-clic), or switch to a slower channel (e.g Monthly Enterprise Channel, or SemiAnnual Channel), until the issue is fixed in Current Channel.  The issue only impacts Decimal types so if avoiding DAO code that manipulates Decimal types is possible, we’d advise this as a short term solution.

Was this answer helpful?

10+ people found this answer helpful.
0 comments

57 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-07-01T11:46:09+00:00

    The issue was fixed a week ago or so, refer to:

    https://support.microsoft.com/en-us/office/access-vba-dao-code-may-crash-or-report-incorrect-data-for-decimal-columns-9311f0ab-ac34-40b4-abd7-2aaa01e07fc7

    My thoughts on Microsoft's update program (both Windows and Office) are already very well known!  They seem unwilling or incapable of fixing things.  It is blunder after blunder, and broken promise after broken promise to change.  You have the choice endure whatever MS continues to output, or switch technologies.  The choice is yours.  I've had a couple of my largest clients switch away from office completely now, and with these latest issues, they are very happy they did!

    As for the pride theme... Outlook is a seperate dev team, but Outlook has made numerous updates recently causing major headaches.

    It's all just more of the same.

    See you around, when the next bug hits, give it a week or two. :-)

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-07-01T06:43:12+00:00

    Good job! After some days we can finally found a solution, we continue to work on it and do the works for microsoft! :)

    Bad....after one month i haven't see an advise, a solution, nothing...you have to search on internet and prey.

    Oh...i just notice a new feature on office...the new pride theme for outlook, this is was microsoft have done in this month. No words.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-06-30T21:39:14+00:00

    Very funny story on the name. I know how you feel. I am getting ready to leave work for the day, but I am curious to see how your inspection regarding are all things equal goes. I am betting you will come across something different from one system to another, or even one user to another. I have even found failing network cards or network medium cause some unexpected issues. It would be interesting if there was a difference in the Windows update state... Good luck on the search!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-06-30T20:08:58+00:00

    (I just learned that a user who's experiencing this crash continually is also on 64-bit 1908 build 11929.20838, so it is no better or worse than others with regard to my issue. These two users have the SAME Access front end database and the same version of Access, interacting with the same back end database, running on the same local network, tied to the same switch that leads to the server room. Yet one crashes continually and the other does not crash. Investigating setup differences.)

    Was this answer helpful?

    0 comments