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-20T16:46:00+00:00

Hi Dan - I tried to rollback the update a couple of times but could not get it working. Perhaps I was doing something wrong, but for whatever reason it just would not rollback.

I agree with you that this would normally be the easiest and preferred solution, but when the rollback does not work, it was great (for me) to have this alternative method of getting MS Access back up and running.
Was this answer helpful?

0 comments No comments
Anonymous

2020-06-20T16:22:46+00:00

Just rollback the update. That is the easiest solution. Even better switch to the semi annual update channel and get away from these monthly update blunders.
Was this answer helpful?

0 comments No comments
Anonymous

2020-06-20T16:02:13+00:00

I agree that the the Insider's update channel may be more unstable that the monthly channel, but in this particular instance I will use it gladly rather than allow my business to stay inoperative for a few more weeks until a fix becomes publicly available for the monthly channel.
Was this answer helpful?

0 comments No comments
Anonymous

2020-06-20T14:04:34+00:00

This isn't publicly available, that is the Insider's track. Hopefully it will be publically available in the next week or so.

PS:. No one should use the Insider's update channel for production, it is a early release and even more unstable channel than the monthly channel.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments