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-06-11T22:43:01+00:00

    Roll back.

    A fix may be weeks away.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-06-11T20:34:13+00:00

    This is a huge issue for us right now! 

    When will this be fixed?

    Should we wait for fix or rollback?

    If the time is short to fix, I'd rather not rollback.

    I just updated to the Current version dated June 9 and it does not remedy the issue,

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-06-11T19:42:09+00:00

    Is this another way in which the problem exhibits itself or an entirely different one?

    This happens in code behind form during this type of call:

    Set vTable = myCurrentDB.OpenRecordset("ALinkedTableInASQL2014sp3DatabaseConnectedWith64BitODBC",dbOpenDynaset, dbSeeChanges)

    vTable.Open

    vTable.AddNew

    Field1 = Form.FieldA.Value

    Field2 = Form.FieldB.Value <-- first field with decimals = Access crashes

    .

    .

    .

    Fieldn = Form.FieldN.Value

    vTable.Update

    vTable.Close

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-06-11T14:52:49+00:00

    I have customers running on the the Runtime version of Access.  Whilst I have been able to downgrade full versions of Access to build 2004,there do not seem to be any instructions as to how to do the same for the Runtime

    Was this answer helpful?

    0 comments