Office 2010 SP1 and Access 2010 Runtime SP1 are broken
Wednesday, July 13, 2011
(Updated Saturday 10DEC2011.) On 28th of June 2011, Microsoft Office 2010 Service Pack 1 and the Access 2010 Runtime Service Pack 1 were issued.
After upgrading my development machine (Win7 x64) and a few clients (Windows 2008R2 x64) to SP1 (x86), I started to get strange issues:
- I use .Net libraries from my Access application and suddenly, even when not instantiating any .Net objects, Access would crash, usually on startup, but sometimes when opening the VBE.
Decompiling and re-compacting the database would be OK, usually once, but the problem would reappear the next time I would restart the application.
- In the Runtime, I would get strange errors, such as The setting your entered isn’t valid for this property, or Action Failed Error Number: 2950, or Runtime Error 3270 Property not found.
The strange thing about these errors is that they would occur in places that had not been modified for many releases of our application, parts that have been running without problem until now.
- Another weird issue was the systematic reset of our custom ribbon to its first tab. this could happen randomly, but most it could also be reproduced by simply opening a report as a tab page (that fill-in the whole MDI window). When closing that form, the first tab of the ribbon would select itself automatically. This wasn’t happening when closing pop-up windows.
After removing the Office and Runtime Service Pack 1, everything went back to normal.
A fix, finally!
A good 6 months after SP1 was released, Microsoft finally issued hotfix for the issue!
So, read about it on the MS Forums and get your KB2596585 hotfix, then decompile your database to clean it out.
Entry Filed under : Database,MSAccess,Programming
4 Comments Add your own
1. Ted Bailey | July 22nd, 2011 at 2:03 am
We are having the same problems EXACTLY the same runtime errors 2950 and 3270 and they only seem to pop up when using the debugger to debug Access 2010 VBA code sitting behind the scenes. We have also had MDE’s that just won’t even start up, and now buttons on Access menu forms that refuse to run and throw very unseemly looking error dialogs, stuff we have never seen the likes of before … MS Access has stopped working yada yada … We have also been getting a lot of problems with filtering. Unchanged code where filters were being applied now dont seem to filter ANYTHING -- the user complaints are starting to roll in … we are VERY concerned to put it mildly … TGB@HWR
2. Carl-Gerhard Wieners | August 16th, 2011 at 3:11 pm
Starting the database with the /DECOMPILE switch then closing and re-open it and compiling again fixes the problem for 2-5 changes. Nevertheless, it is very annoying.
3. Arturo Villar | October 6th, 2011 at 10:20 am
I have the same problem. I use 32-bit Access SP1 on W7. My mdb crashes inconsistently. This mdb uses linked tables with SQL Server. The crash only happens to me when I’m developing in my own equipment. When it ocurres I use the /decompile option and the problem is soved. There are not crashes for 80 people that uses the app
4. Craig | November 22nd, 2011 at 4:38 pm
Same problem, while devloping Access just crashes and i loose all my work.
I have now decompiled and recompiled the DB’s after applying the MS hotfix, but still remote users are getting blank forms for appilcations that work fine for in-house users.
If I take the same application and compile it using Access 2007, the app works fine for remote users, as it was working prior to SP1 2010.
This has to be one of the worst balls ups I have seen MS make since releasing Vista!
My users are not happy and neither is the Boss!
Leave a Comment
Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
Trackback this post | Subscribe to the comments via RSS Feed