So we're having an interesting problem at work. I'll try to detail the full situation.
Basically, I just switched positions at work to a new department. In my last department I was making a lot of Excel Macros (as well as managing a large Access database). In that position I had office 2010 and MS Project 2003 (because of some legacy programs we were stuck on 2003).
There were never any problems with people running any macros I made that were initiated by clicking an ActiveX Command Button.
In my new position I am still using Office 2010 but I had to have Project 2013 installed because they have a SharePoint site setup that requires that version. After restarting my computer after installing Project 2013 a bunch of updates were installed that IT had just released, included in that was the dreaded Microsoft Security Bulletin MS14-082, which caused all ActiveX buttons on my machine inside of Excel to stop working. Luckily, I found Microsoft's security fix for the problem and was able to resolve the issue on my computer.
Unfortunately, I needed to make an update to one of the macros that I made for the previous group and after sending out the new file no one in the previous group is able to run them. The only difference from their computers and mine is that I have Project 2013 but we both have office 2010. At first I assumed it had to do with the Microsoft patch and they needed to preform the fix. But after doing that on their computer they still cannot run the file. I also tried recreating the file on my computer (make a new button and copy the code from the old file) but that still doesn't work on their computer even though it works perfectly fine on my computer. Finally I recreated the file on their computer doing the same thing and then the macro would run just fine on their computer.
Someone in my new group has office 2013 and he is able to run my macros just fine. So finally, I had him create a simple macro where you push a button and a message box pops up on his computer and I'm able to open it but none of the other users who have just office 2010 can run it.
Sadly I don't know if the compatibility issue is a result of the Microsoft patch or if office 2013 ActiveX has always been incompatible with previous versions. Also, it seems weird, but I don't know if installing Project 2013 somehow changed my Excel Library reference to a different version than theirs. I know this is a very specific situation, but has anyone else has any experience with this or know of any solution for this?
Luckily, I haven't had to touch the Access Database since the change, but that one contains thousands of lines of code spread over many many forms and many many command buttons. So just recreating it on someone else's computer isn't an option.
Any help or suggests would be very much appreciated.
Jason
Bookmarks