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.
Are you sure SP1 is the problem? Create a new ACCDE and have your user try it. Could be that the first one is corrupt.
I am not sure it is SP1 exactly, however, it is giving this error on other databases saved this week. Something changed recently and ACCDE files created prior to this week work fine, those done today are not opening.
I am not sure it is SP1 exactly, however, it is giving this error on other databases saved this week. Something changed recently and ACCDE files created prior to this week work fine, those done today are not opening.
Can you back out SP1? MS usually has uninstalls available in the control panel. Make sure the "Show Updates" is checked.
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.
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.