Access crashes since latest (June) Office 365 update 16.0.12827.20268

Anonymous

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

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

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.

0 comments

57 additional answers

Anonymous

2020-06-13T02:10:12+00:00

I appreciate the input SkutrBall. I am not sure all things are equal, but based on your feedback, I will give it a go again.
Was this answer helpful?

0 comments No comments
Anonymous

2020-06-15T11:04:49+00:00

Hello,

Reverting to prior versions of office did not work for me either and my whole production is stalled. I found one computer that is able to work with fresh install of Office 2019 (and no updates) but it does not work with the other computers, there must be a combination of multiple factors.

Please provide very quickly a workaround that really works because it has been several days without being able to even emit an invoice because of this bug.
Was this answer helpful?

0 comments No comments
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 No comments
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 No comments