This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I recently allowed my Access 2013 to update itself to SP1 or the latest version. Today I modified a database and saved it as a ACCDE file. When one of my Access 2013 runtime users attempted to open the database they got an "unrecognized format" error. I searched for an updated Access 2013 runtime for SP1 and there isn't one. This is a big problem as all of my users use the runtime to open and use the databases. I effectively cannot update or revise any database design until this issue is resolved.
Is there an ETA on when the runtime will be updated? If not is there a work around?
A family of Microsoft relational database management systems designed for ease of use.
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.
I am going to try a windows rollback on one of my windows's 7 computers and then disconnect it from the internet so it doesn't re-update. I'll create .accdr files from that computer for my runtime users until Microsoft gets around to solving this.
I'll report back here if it works.
OK... Glad someone else out there is having the same issue. Hopefully, it is on Microsoft's radar. I would imagine having deployment problems when using runtime is going to effect more than just us. Alot of people are going to wonder what the heck is going on.
Rolling back didn't solve the problem? That is not encouraging.
I have the same problem too! I have several computers running windows 7. One computer has Access 2013 which was used to build an application. This application is then shared with the rest of the computers which run Access 2013 Runtime.
Today I attempted to deploy a newer version of the database and all the computers running the Access Runtime were unable to open it. It appears Access updated itself to a version which breaks new accde files.
I attempted to roll back to a version several months old using integratedoffice.exe REPAIRUI RERUNMODE version 15.xxxxxxx but it failed to change the version number.
PLEASE FIX THIS IN THE NEXT UPDATE
(http://www.slipstick.com/outlook/2013/uninstall-update-office-2013-click-run/)
I also have the same problem! I have multiple computers running Windows 7 with the most current version of Access Runtime 2013 as well as WIndows 7 & 8 computers running Office 2013 professional
I cannot isolate which update officially caused this problem, it may have been SP-1, it may be another. But I physically watched it propagate through the office.
Any computer running full blown Access 2013 is affected. If the database is compiled and saved as .accde or .accdr from the updated computers running full blown Access 2013, the resulting file can be opened by anybody running updated version of full blown Access 2013 but not any of the computer running Access Runtime 2013 only.
Here is the kicker, for awhile I had one computer running full blown Access 2013 that had not updated itself yet, and if I compiled and saved from that computer, then the file worked from all computers (Runtime computers, updated Full Access 2013 computers, non update Full Access 2013 computer) Once that computer finally updated, it now shows the same issue. I now have no computers that can effectively save a database as an .accdr and then be recogonized by access runtime 2013.
I wish I knew which update did this... I absolutely need resolution to this problem as my runtime users need updated databases.
What I can do is not save the database in the ACCDE format. Users can then open the files. Just seems like if the full program gets updated the runtime should as well. Not happy with this but what choice do I have at this time. I will just hold off saving as ACCDE until MS gets the runtime updated.