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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-06-18T17:52:14+00:00

    Nicolas: There is something to what you are saying. I am starting to come across similar and multiple new issues that go beyond Access alone. I need to study it more though. I am going through a chain of discovery and research that all started with the issue we are discussing and this particular issue that Microsoft seems to have addressed on 6/16/2020: https://docs.microsoft.com/en-us/office/troubleshoot/excel/excel-opens-blank . The timing is no coincidence, so I expect we are going to see more problems with not only Access, but across the Office suite, into Windows 10, and beyond. I hope I am wrong...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-06-18T18:04:32+00:00

    With every patch Tuesday, we see some issues fixed, but also, the introduction of new bugs throughout the entire office ecosystem.  I formally know if reports of major issues with Outlook, Excel and Access.  This is nothing new and has been happening for a good 5 years now.

    Same is true of Windows Updates.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-06-18T18:20:05+00:00

    Please advise, is there a way to keep Access365 runtime from updating itself?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-06-18T19:28:05+00:00

    I hear you on that. In Microsoft's defense, the OS and how it relates to all of the apps that run on it is very complex; but, it seems like their regression testing is flawed, or maybe their testing in general. I think they are getting ready to take a different turn regarding a new vision and how it is applied most especially regarding their operating system offering(s). Maybe this will help. Maybe it will simplify parts of their model that are overly complex now. Maybe...

    Was this answer helpful?

    0 comments