Yes, it has been reported, and confirmed by many now, that one of Microsoft’s updates (KB3085515) released March 8th, 2016 breaks MS Access. From what I’m seeing it appears to limit itself to affecting only Access 2010 compile versions of databases (accde, ade, accdr and I’m assuming mde files). Accdb seem to continue to work normally.. Others even report it affecting accdb files, so it appears to potentially impact any 2010 database file.

So if you wake up this morning and you are having issues with your database that previously worked just fine, then check and see if KB3085515 was installed recently, and if so uninstall it.  You can find Microsoft’s detailed instructions for uninstalling this update at: March 8, 2016, update for Office 2010 (KB3085515).

For more details on this problem, see: KB3085515 breaks MS Access 2010 reference.

I reported the issue, after seeing the thread pop-up yesterday evening (Gina Whipp brought it to the attention of the Access MVPs), to the proper authorities at Microsoft. So, they have been made aware of the issue and let’s just hope Microsoft pushes another update to fix this flawed update soon!

Update 2016-03-10

Also, the Access Dev. Team finally made a post on their blog about the problem and are supposed to eventually post more information, so you may want to keep an eye on:

You may encounter errors with your ACCDE/MDE files and/or wizards after installing the March update for Office 2010 (KB3085515)

Update 2016-03-11

Several people have reported that even uninstalling the update that cause all these problems did not undo the damages it caused and that they solution was to manually replace VBE7.DLL file put in place by the update with a prior version they found by searching their computer:

For me the unistalling of the KB did not work unfortunately. But reading the about the update of the VBE7.DLL made me experiment a bit. I searched my machine for all versions of this DLL and found one with version 7.0.16.28 (this was the newest before the update on my machine) Renaming c:\Program Files (x86)\Common Files\microsoft shared\VBA\VBA7\VBE7.DLL to VBE7.OLDDLL and then copying the older version of the DLL to this location solved the problem for me, fortunately.  – Hans Peter