Access – Bug – 1710 Breaks Compatibility with ACCDEs and Access Runtime

It’s been a rough year for the Access Development Team and Updates! Sadly, Update 1710 is no exception to the rule.

First reported in the Microsoft Answers forum by JDKilmer and now confirmed by the Dev Team, it would appear that update 1710 breaks compatibility between ACCDEs and Access runtime. Access generates the “unrecognized database” error:

This database is in an unrecognized format. The database may have been created with a later version of Microsoft Access than the one you are using. Upgrade your version of Microsoft Access to the current one, then open the database.

There is no workaround beside not installing the update in the first place, or reverting back (see: Microsoft Office 365 – Uninstall an Update) if you already have it installed. Don’t forget to disable updates or else you just find yourself back facing the same issue again.

Let’s keep our fingers crossed that the Dev Team can promptly push out a fix to address this issue as it is kind of critical.

Update 2017-11-10

Microsoft has added the issue to their Fixes and Workaround page, see: https://support.office.com/en-us/article/Fixes-or-workarounds-for-recent-issues-in-Access-54962069-14f4-4474-823a-ff7e5974a570?ui=en-US&rs=en-US&ad=US (under the heading Error: “This database is in an unrecognized format” when opening .accde file [WORKAROUND]), but sadly, they provide no more information than what is already provided above. They simply redirect the reader to another page that states you have to revert your installation to a previous build (just as stated above, except it takes them 2-3 pages to tell you!)

Update 2017-11-20

Microsoft reports having released an update that resolve the issue. According to the Nov 20th release notes relating to Version 1710 (Build 8625.2132) :

Access: Non-security updates

This channel release contains the following non-security updates:

Fix an issue where opening an Access runtime application (.accde file) results in a “This database is in an unrecognized format” error message and the application won’t open.

So try performing a manual update to build 8625.2132.

16 responses on “Access – Bug – 1710 Breaks Compatibility with ACCDEs and Access Runtime”

Regi November 10, 2017 at 8:02 am

Thank you to share with us!

John D. November 10, 2017 at 7:48 pm

I’ve experienced compatibility issues between version running an accdb on the full version of access. I had some users on 1710 and others on 1709 and those on 1709 would see the database container momentarily flash before their eyes and then close. Updating their PCs to 1710 fixes the issue. So, IMHO, the issue is much more widespread than just impacting accdes being run in runtime.

Daniel Pineault Post authorNovember 10, 2017 at 8:13 pm

I’ve experienced the exact same thing with one of my client this past week.

Andy November 14, 2017 at 9:23 am

We have several RDP servers running MS Access-runtime. I’ve been working on a fix and some updates that I went to deploy this morning, only to see this error. At first, I thought it was me, so I spent my morning rebuilding my application and trying earlier versions. I only realised what it was, when I created an Access database, with a single form, compiled it and pasted the file onto the server – yep….that’s when the penny dropped.

Andy November 14, 2017 at 9:35 am

What seems to be making this more fun – is that I can’t see the update in “Update & Security”, just major updates. Plus, my RDP servers are running Server 2012 R2 – so the update needed to move forward hasn’t been released. Thank you M$.

PS – Thanks for posting this article – a really interesting site.

Matthias Kläy November 21, 2017 at 4:56 am

Microsoft has fixed the bug, see
https://technet.microsoft.com/en-us/office/mt465751.aspx

November 20, 2017
Version 1710 (Build 8625.2132)
Note: Current Channel is now named Monthly Channel.
Access: Non-security updates
This channel release contains the following non-security updates:
Fix an issue where opening an Access runtime application (.accde file) results in a “This database is in an unrecognized format” error message and the application won’t open.
I can confirm that the .accde’s built with this version now work on the runtime again.

Daniel Pineault Post authorNovember 22, 2017 at 6:12 am

Thank you for the update.

Peter Leighton November 28, 2017 at 12:22 am

Hi
How do I download and install this build 8625.2132.

Daniel Pineault Post authorNovember 28, 2017 at 11:55 am

Take a look at How to Manually Update Access/Office 2016.

You can also use the same approach to revert to a specific build (even if in fact it is an update). So you could follow the instructions from Microsoft Office 365 – Uninstall an Update.
1. Ron Mittelman February 16, 2018 at 2:26 pm
  
  Hi Daniel,
  I’m not having this particular issue, but related: When I update our Access application on my development PC (which has only Office 2016) then build the accde and deploy it to my users (who have only Office 2010, but no Access, just runtime), I get the same error.
  This is gotten around by copying my 2016 accdb to older development PC (which has only Office 2010) and recreating the accde. That then works on other client PCs.
  So the question is: Is this expected behavior, and ongoing this is the way to issue upgrades, or is there a way I can build the accde on the 2016 machine and have it work on older 2010 PCs?
  
  Thanks in advance…
  1. Daniel Pineault Post authorMarch 10, 2018 at 7:03 am
    
    Yes, this would be the expected behavior. Access is backwards compatible meaning 2016 understands older versions ie 2010, but no software is forward compatible. Therefore, there is no way for 2010 to understand all the changes to the file format, data types and other features that were introduced in 2013+. As such, when you try to open a newer version of a database within an older version of Access then that used to create it you receive the beautiful “This database is in an unrecognized format. The database may have been created with a later version of Microsoft Access than the one you are using. Upgrade your version of Microsoft Access to the current one, then open the database.” error message.
    
    This is why the golden rule of development is to always perform all development using the oldest version of the application that will be used to run the program. So in the case of having Access 2010 and 2016, you need to do all your development in 2010, knowing that 2016 will automatically be able to run the 2010 version without issue.

ZTatZAU March 20, 2018 at 2:52 pm

Daniel,
I’m happy to have found this thread!
Can you tell me how to determine if this latest update (8625.2132) has been installed? I know how to find the Access 2016 version (16.xx.xx, etc) but where do I find the “Build number”? And, is this an Office 2016 update or an Access 2016 update?

Thanks for sharing your knowledge and expertise with others!

Daniel Pineault Post authorApril 3, 2018 at 7:23 am

Click on the File Tab
Click on the Account button
Then under Product Information you should see a line similar to “Version 17xx (Build xxxx.xxxx) …”

ZTatZAU March 20, 2018 at 4:55 pm

FOLLOW UP!
I’ve just received the following version information from my client…
Office 365 – Microsoft Access 2016 MSO (16.0.8528.2126) 32-bit.

I am unsure as to whether or not the last pair of 4 digit numbers in the above version directly correspond to the “build number”, 8625.2132′ referenced above as the fix for this bug; nor how the above information relates to the 1709 and 1710 (updates?) referenced above. Can you decode all this for me as to whether this Office installation is, or will be if auto updated, subject to this known runtime issue?

Thanks again!

Daniel Pineault Post authorApril 3, 2018 at 7:28 am

From what I can tell from reviewing https://support.office.com/en-us/article/Version-and-build-numbers-of-update-channel-releases-ae942449-1fca-4484-898b-a933ea23def7 build 8528.2126 is very old (in relative terms of course) version 1709. They are now up to 9126.2116 version 1803. Your client should be trying to update. They may have to first switch Update Channels to gain access though. It’s a horrible mess to manage in Office365/2016.

ZTatZAU April 3, 2018 at 8:58 am

Thanks again Daniel!
ZT

Regi November 10, 2017 at 8:02 am

Thank you to share with us!
John D. November 10, 2017 at 7:48 pm

I’ve experienced compatibility issues between version running an accdb on the full version of access. I had some users on 1710 and others on 1709 and those on 1709 would see the database container momentarily flash before their eyes and then close. Updating their PCs to 1710 fixes the issue. So, IMHO, the issue is much more widespread than just impacting accdes being run in runtime.
1. Daniel Pineault Post authorNovember 10, 2017 at 8:13 pm
  
  I’ve experienced the exact same thing with one of my client this past week.
Andy November 14, 2017 at 9:23 am

We have several RDP servers running MS Access-runtime. I’ve been working on a fix and some updates that I went to deploy this morning, only to see this error. At first, I thought it was me, so I spent my morning rebuilding my application and trying earlier versions. I only realised what it was, when I created an Access database, with a single form, compiled it and pasted the file onto the server – yep….that’s when the penny dropped.
1. Andy November 14, 2017 at 9:35 am
  
  What seems to be making this more fun – is that I can’t see the update in “Update & Security”, just major updates. Plus, my RDP servers are running Server 2012 R2 – so the update needed to move forward hasn’t been released. Thank you M$.
  
  PS – Thanks for posting this article – a really interesting site.
Matthias Kläy November 21, 2017 at 4:56 am

Microsoft has fixed the bug, see
https://technet.microsoft.com/en-us/office/mt465751.aspx

November 20, 2017
Version 1710 (Build 8625.2132)
Note: Current Channel is now named Monthly Channel.
Access: Non-security updates
This channel release contains the following non-security updates:
Fix an issue where opening an Access runtime application (.accde file) results in a “This database is in an unrecognized format” error message and the application won’t open.
I can confirm that the .accde’s built with this version now work on the runtime again.
1. Daniel Pineault Post authorNovember 22, 2017 at 6:12 am
  
  Thank you for the update.
Peter Leighton November 28, 2017 at 12:22 am

Hi
How do I download and install this build 8625.2132.
1. Daniel Pineault Post authorNovember 28, 2017 at 11:55 am
  
  Take a look at How to Manually Update Access/Office 2016.
  
  You can also use the same approach to revert to a specific build (even if in fact it is an update). So you could follow the instructions from Microsoft Office 365 – Uninstall an Update.
  1. Ron Mittelman February 16, 2018 at 2:26 pm
    
    Hi Daniel,
    I’m not having this particular issue, but related: When I update our Access application on my development PC (which has only Office 2016) then build the accde and deploy it to my users (who have only Office 2010, but no Access, just runtime), I get the same error.
    This is gotten around by copying my 2016 accdb to older development PC (which has only Office 2010) and recreating the accde. That then works on other client PCs.
    So the question is: Is this expected behavior, and ongoing this is the way to issue upgrades, or is there a way I can build the accde on the 2016 machine and have it work on older 2010 PCs?
    
    Thanks in advance…
    1. Daniel Pineault Post authorMarch 10, 2018 at 7:03 am
      
      Yes, this would be the expected behavior. Access is backwards compatible meaning 2016 understands older versions ie 2010, but no software is forward compatible. Therefore, there is no way for 2010 to understand all the changes to the file format, data types and other features that were introduced in 2013+. As such, when you try to open a newer version of a database within an older version of Access then that used to create it you receive the beautiful “This database is in an unrecognized format. The database may have been created with a later version of Microsoft Access than the one you are using. Upgrade your version of Microsoft Access to the current one, then open the database.” error message.
      
      This is why the golden rule of development is to always perform all development using the oldest version of the application that will be used to run the program. So in the case of having Access 2010 and 2016, you need to do all your development in 2010, knowing that 2016 will automatically be able to run the 2010 version without issue.
ZTatZAU March 20, 2018 at 2:52 pm

Daniel,
I’m happy to have found this thread!
Can you tell me how to determine if this latest update (8625.2132) has been installed? I know how to find the Access 2016 version (16.xx.xx, etc) but where do I find the “Build number”? And, is this an Office 2016 update or an Access 2016 update?

Thanks for sharing your knowledge and expertise with others!
1. Daniel Pineault Post authorApril 3, 2018 at 7:23 am
  
  Click on the File Tab
  Click on the Account button
  Then under Product Information you should see a line similar to “Version 17xx (Build xxxx.xxxx) …”
ZTatZAU March 20, 2018 at 4:55 pm

FOLLOW UP!
I’ve just received the following version information from my client…
Office 365 – Microsoft Access 2016 MSO (16.0.8528.2126) 32-bit.

I am unsure as to whether or not the last pair of 4 digit numbers in the above version directly correspond to the “build number”, 8625.2132′ referenced above as the fix for this bug; nor how the above information relates to the 1709 and 1710 (updates?) referenced above. Can you decode all this for me as to whether this Office installation is, or will be if auto updated, subject to this known runtime issue?

Thanks again!
1. Daniel Pineault Post authorApril 3, 2018 at 7:28 am
  
  From what I can tell from reviewing https://support.office.com/en-us/article/Version-and-build-numbers-of-update-channel-releases-ae942449-1fca-4484-898b-a933ea23def7 build 8528.2126 is very old (in relative terms of course) version 1709. They are now up to 9126.2116 version 1803. Your client should be trying to update. They may have to first switch Update Channels to gain access though. It’s a horrible mess to manage in Office365/2016.
ZTatZAU April 3, 2018 at 8:58 am

Thanks again Daniel!
ZT