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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-06-15T16:08:20+00:00

    Thanks for the input Daniel. I will take a look at the back-end, but I fear a change of the datatype may not be an option for us. There are lots of calculations involved and the places beyond the decimal are highly critical and have to be defined. I do have a plan in hopes that the fix is approximately 2-3 weeks out. Fortunately the user systems are still mission specific at this point. I am just going to reset the systems back to factory default and temporarily turn off updates until the fix is out. While it might be irritating, it is really not all that difficult to do. Just to avoid and extra complications, I have done the same thing with the SQL server--no updates for now. Thanks all! You made the decision easier to make.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-06-15T14:03:49+00:00

    Well, the only difference it makes is that instead of crashing, it returns a 'Data type mismatch in criteria expression'.

    Actually, I could not rollback to the 2004 version, I tried several ways, with the Office deployment tool I the equivalent version of the 2004 (10357.20081), otherwise with a classical installation, the only rollback version that works is the 1809 (16.0.10827.20181)

    "C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe" /update user updatetoversion=16.0.10827.20181

    I used other versions but in this case it does not work (it does not display the orange screen of the updates).

    Do you have any idea why I get this behaviour ?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-06-15T12:16:04+00:00

    From what we've been told you can expect 2-3 weeks before a fix is available and of course there are no guarantees (could be sooner, could be later).

    Rolling back to version 2004 is the only solution for the time being, otherwise you'll have to wait.

    Other MVPs also ask if you cannot change to field so it isn't decimal, as only decimals are impacted by the present bug.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-06-15T11:31:44+00:00

    We have the same error in Access and using VBA code.

    Was this answer helpful?

    0 comments