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-12T16:17:12+00:00

    I have begun noticing a lot of issues in MS Access Office 365 C2R since the latest June update.  Using VBA to query tables with certain combination of fields causes Access to close without warning.  Editing a code module on a form with a large list view freezes Access cold without closing it.  Querying data sets using VBA returns corrupt data. I verified this latter item is the case with SQL linked tables as well as with an internal MSAccess table. I have created a sample database that exhibits some of these issues. Using Access 2013 everything is just peachy good. ??!? 

    I can open tables to read data directly and even design and use queries to pull and read and write data just fine.  All these crashes appear to originate when VBA code is executed and/or COM+ or code calls to memory objects are invoked. It is not always consistent. Sometimes stepping through code it is fine but data is still corrupt. Other times stepping through code line by line Access just vanishes off the screen and out of memory. Did something go sideways recompiling the VBA interpreter?

    I have started getting calls from clients who are becoming affected by this issue and so far have a dozen affected people in two companies plus my own workstation. I am concerned this is a widespread issue that if everyone updates it will kill functionality of  MS Access for my entire client base (everyone). This has happened once already last year with the "Query is Corrupt" bug that took over 4 weeks to resolve.  Very concerning that MS Access is no longer the stable product that has led so many to use it for effective business solutions. Let me know what I can do to assist and so we can get the CR2 update path fixed before too many more get hit with issues?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-06-12T08:27:22+00:00

    Was this answer helpful?

    0 comments
  3. 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
  4. 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