Access 2013 runtime and SP1

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!

• ****! I have spent ALL DAY trying to figure this out before reading all of this! I'm using Access365 Home Premium.
• Access2013 successfully installed on client's PC, but it won't open the ACCDE with the "wrong version" message.
• Just for fun, (sarcasm) I copied my ACCDB file to the client's PC and I can open IT.
• Sure, the runtime won't allow me to view designs, etc ... but am I about to deploy my app without any means of protecting my valuable code? I don't think so!
• I hate to be cynical, but do you suppose this has anything to do with Money$oft's new "App Store"? Are they forcing use to use that as the only means of distributing an app? Is that why they discontinued the "Installation Packager Wizard" with this version?
• I even tried that, using the wizard in Access 2007 (which creates an ADDR file). It fails with same error. Aaaaaaaaaaarrrrrrrrrgggggg!!!!! PS: The only way to be able to upload/distribute through the Office Store is to have a copy of the Business version, right? Am I going to throw another couple hundred to Money$oft for that priviledge,,and have 2 different "versions" of the same software? This is total BS.

UPDATE # 2 - FAIL

What I thought was a success in terms of rolling back windows was short lived.  The database did indeed open on the runtime machines, but after some use, there are major errors that are appearing having to do with the use of DAO.recordset.  Upon .edit I'm getting ERROR 3320 "Function is not available in expressions in table-level validation expression."  This is occurring anywhere a DAO.recordset is used in code. These errors are again obviously not present on the full Access 2013 computers that had the update.

I am back to not having workable distributions for my runtime users.

Full Fledged Access DB files work fine, confirmed this is just the ACCDE version....this sucks..