locked
June 2 Office Update Crashes Access RRS feed

  • Question

  • Hello,

    On June 2, we received an automatic update of Microsoft 365 (including Office) and this has caused our Access frontend to crash. I'm pretty sure there is some VBA code that it didn't like. I didn't have a chance to step through the code to find where the crash was, but it was happening on multiple forms. We had to roll back 365 to the May 21 update (12730.20352) and disable automatic updates. 

    The switchboard would open, but when a form with a lot of code behind opened, Access completely closed. On another form, we were getting an Error 13: Data Type Mismatch (this didn't occur on PCs that hadn't been updated). Other users said that the got the "Microsoft Access Has Stopped Working" message.

    I was wondering if anyone else had this problem, and if they had found what was causing it. I don't have a test PC to run it on, so any help appreciated!

    Thank you,

    Albert


    Albert S

    Tuesday, June 9, 2020 8:32 PM

Answers

  • Hi,

    yes, many people have this crash problem with the latest versions. MS is working on a support article. Meanwhile this is the information by the Access team:

    ************
    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.
    ************

    UPDATE: The support article has been published. The info about a fix will be published there too.

    Karl

    Access DevCon Vienna
    donkarl.com


    Wednesday, June 10, 2020 8:15 AM

All replies

  • Hi,

    yes, many people have this crash problem with the latest versions. MS is working on a support article. Meanwhile this is the information by the Access team:

    ************
    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.
    ************

    UPDATE: The support article has been published. The info about a fix will be published there too.

    Karl

    Access DevCon Vienna
    donkarl.com


    Wednesday, June 10, 2020 8:15 AM
  • Excellent. Thank you for this update. As I traced through the code it seemed a new date field we recently added was causing the problem.

    Take care,

    Albert


    Albert S

    Wednesday, June 10, 2020 3:46 PM
  • I can't believe Microsoft F'd up again.  This is the second time.  It happened November 2019.

    https://social.msdn.microsoft.com/Forums/office/en-US/538c2c33-d30e-48b5-a77b-aafee63c71e3/latest-office-20072010201320162019-update-breaks-access-query-query-is-corrupt?forum=accessdev


    If this post answered or helped you find the answer to your question, please mark it as such for other Forum users knowledge.

    Sunday, June 14, 2020 11:59 PM