Access 2013 runtime and SP1

You also have to realize that not all target machines have MS Office which is why the runtime is being installed. In that case, the SP1 Office Update won't be installed.

JuanMas53 do you think you can give detailed instructions on how you uninstalled the update? Thanks.

I went to Windows Update and clicked "Installed Updates".  I then searched for "sp1" and found "Service Pack 1 for Microsoft Office 2013 (KB2850036) 64-Bit Edition". I then clicked on that entry which revealed an uninstall link in the upper left corner of the window. Clicking the uninstall link will uninstall the service pack.

Hi Albert, my last statement was a little too much on the dark side. Not clear enough.

What I meant by that was to rewrite my application in vb.net to avoid issues with Office 365 pro vs Office 365 plus vs Office Std with Access runtime. I know .net has its issues, Windows Updates will show up and break things, just like Office, but at least I wont have to deal with what it seems to be different "versions" of the same product (Office 365 vs Standard/Pro/run-times or viewers).

You are correct about everything you said, but the simple solution is not that simple as you can see by the comments in this forum. SP1 obviously broke something (as always), but the kicker is that 3 identical systems with Office 365 with the same version throw the "unrecognized format" error. SP1 one won't install in these systems because they have the "Office 365" version of the programs. So the step of ensuring the target machines have the same version as the machine where the software was compiled goes out the window (no pun intended), now what? isn't that laughable on their part?

Well, thanks for your comments, I just wish they (Microsoft) would test their updates before releasing them, specially in mixed environments, but then again, the Team may not have time for little things like that, after all, maintaining the multitude of color themes (3) and figuring out ways of wasting vertical space with their "ribbon" menus takes some serious brain power. I wonder if they know that nowadays most screens are wide-screens and that they are shorter than back in the day.

I don't think my environment is unique, only one dev machine with the full version of Access to compile and x number of target machines that should not need anything but the runtime to run it.

Oh well, even if we were to waste the money getting everyone into Office 365, still would not work.

One wonders who signs their paychecks.

Thanks

Shouldn't have to go to those lengths but...

No, we sure shouldn't.

Microsoft just needs to TEST and issue updates to BOTH the full version and the Runtime concurrently. Period. Exclamation Point.

Great, keep up the squeaking... if we squeak enough then at least it has a chance to be on the radar for fixing.  I agree with your post about us "hobby" programmers and just expecting it to work.

I'm taking Albert's suggestions seriously here, should have an answer by Monday whether or not his claim truly rectifies the issues. But the fact is, what Albert assures us is "common" knowledge is far from that.  Again, I've been at this hard core for 15 years and never even remotely ran into anything like this issue, despite Albert's assertion that of course I have, I just didn't know it. 

You're right, I just expect the damn thing to work correctly, my business cannot afford for it not to.

This has been a wake-up call for me... once this thing blows over. I'm going to take flash images of one of the machines in working state as well as a copy of the database application and backend from that date and file it away.  Microsoft does this again, I re-flash the computer, remove from the internet, and keep my business running without a hitch.

Shouldn't have to go to those lengths but...