Access 2013 runtime and SP1

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?

I have confirmed that the culprit is MS OFFICE 2013 SP1 update. I was having the same problem with .accde files not being recognized by the 2013 runtime. Interestingly, the .accdb file runs perfectly under the runtime. My target PC runs Windows 8.1 and my development PC runs Windows 7.

I solved the problem by uninstalling the MS OFFICE 2013 SP1 update. Now my .addbe files run perfectly under the runtime.

I have the same problem!! My Office 2013 has an auto update.

This Version is 15.0.4605.1003

I can not distribute my Software and many Updates!!

Access Runtime 2013 Version is: 15.0.4517.1004

Office 2013 generate a wrong File (x.accde) for Access Runtime 2013 !!!!!!

Hopefully Microsoft launches as soon as possible for Access Runtime an update out !

Dan,

You miss the point, we can't distribute. No runtime user can use our outputed files. Only full blown access users can open our databases.

I've been using Access for 15 years, I've had times where updates through me for a loop... but I never had a situation where I could not distribute my database revisions to my runtime users. I don't design databases to sell, I design databases to make my business run better. Try telling Microsoft that, I think they need a refresher.

Well Don,

I Understand the frustration... I've just about tried it all:

Deleted registry keys, windows restores, reinstalls, repairs, tried tricking runtime with known un-updated copies of Access etc. Nothing worked, whatever the change is, it is internal to the operating system components of access and is persistent once installed, and runtime doesn't like it. No way around it.

At a certain point, I had to make a buisness decesion. If I waited for Microsoft to get around to fixing runtime (which if you look, has not been revised in more than 6-8 months) I'd be out of buisness.  That is not acceptable.  I will not let a billion dollar bafoon put my small buisness out of buisness with incompetence.

So, even though it feeds the beast, I went and purchased standalone Full versions of Access for all my runtime machines even though they don't remotely need it, in effect giving Microsoft hundreds of dollars they don't deserve.

In the end, no update should bring my process computers down to the point of not functioning. Unacceptable. Period.

I'm back up and running, am not using runtime until further notice and obviously have select words for any Microsoft employee that cares to listen.

Sadly, there have been a number of problems with Office 2013.

But I don't understand your statement: "Are they forcing use to use that as the only means of distributing an app"?  You can zip up your database and sell it on your site, or any site for that matter.  You can use any other packaging software and distribute that instead and actually they often much better than MS' offering!