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

    Roll back.

    A fix may be weeks away.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-06-11T22:49:55+00:00

    I experienced the same here, it seems that multiple libraries are involved in this error. 

    Pad naar module met fout: C:\Program Files\Microsoft Office\root\Office16\acedao.dll

    Pad naar module met fout: C:\Windows\System32\OLEAUT32.dll

    Pad naar module met fout: C:\Windows\SYSTEM32\ntdll.dll

    During my search I noticed strange results. A Query including a calculated decimal variable was working, but DAO provided results as already mentioned here (?????? or ""). Using DLOOKUP however showed the right value. I managed to solve this by putting *1 after the calculated field in the SQL. In other situations I could not resolve this because there was no SQL query involved. I experienced the errors occurred most of the time when a decimal value in a variable is evaluated (for example If variable < value). I stopped further searching and updating the VBA code for trying workarounds (too much work) and I cannot wait for the update solving this issue. My app involves time registration and must be available at any time. I now rolled back to build 16.0.12730.20250 and disabled updates for now. 

    Very disappointing that happened, took me a day to find the actual cause of the error.

    Art.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-06-12T02:21:05+00:00

    Daniel,

    Thanks for your insight, I will be taking time tomorrow to roll back Office on a handful of PCs my client needs to have working without this error. That, of course, will wind up being a direct quantifiable expense to them as they don't have an IT staff of their own.

    Microsoft needs to recognize that not all sophisticated businesses have IT staffs whose general expense absorbs hits like this.

    Cheers

    F. X.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-06-12T07:06:49+00:00

    For anyone wanting to have a easy script to rollback the office update to a previous one, execute this in the run box (Windows + R):

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

    Was this answer helpful?

    0 comments