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-08T12:53:32+00:00

    Hi nico,

    Thanks for sharing your experience here and sorry for the inconvenience caused by this issue.

    According to your description, we did a test from our side with Version 2004 (Build 12730.20352) but fortunately, we can reproduce your issue.

    In this case, we found a similar thread with the same Exception code: 0xc0000374 you can follow the providing suggestion to check if it works even though it occurred in other Office software:

    Office products crashed upon launch (0xc0000374exception)

    Besides, please try to press the Ctrl key and click Access shortcut to run Access in safe mode to check if this issue is related to third party add-ins.

    You can also try to close your anti-virus program which you are using with MS Access temporary to avoid the conflicting situation, you can turn on your anti-virus back after finishing up the complete work

    If this issue persists, could you share the following information when you have time:

    1.As we noticed that this issue happened when you opening forms in Access, please try to create a new file to check if this issue related to a specific file.

    1. Could you share your product information via File>Account like that:

    Please have a try and share the result with us.

    Best Regards

    Higgins

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-06-08T13:47:37+00:00

    Microsoft updates have become more and more unstable, as you are seeing firsthand.  I'd recommend you rollback to a prior build and wait for Microsoft to sort things out.

    Your build number indicates you are using the Monthly Update channel.  I'd recommend you steer clear of Insiders and Monthly Update Channels as they will always be the most volatile.  You should probably switch over to the Semi-Annual (Targeted), and even then that is no guarantee.  Your other option is to control all updates manually, so wait for updates to be out and tested by the masses before applying it yourself.

    Was this answer helpful?

    0 comments
  3. Tom van Stiphout 40,216 Reputation points MVP Volunteer Moderator
    2020-06-08T15:52:51+00:00

    MSFT is interested in learning more about the problem of opening a large form followed by a crash. Is there a way you can confidentially make a repro scenario available?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-06-09T11:32:34+00:00

    Eventually we created a Group Policy with which we downgrade the Office version to the May update. In this build all seems to work fine. We also disabled Office Updates for the time being, until there is a solution for this bug.

    Thank you for the quick response.

    Was this answer helpful?

    0 comments