First, I am aware of the nearly ubiquitous issue with ActiveX controls and the Dec 2014 MS Excel update. This appears to be different than the common symptoms, but it may be related.
Symptoms:
Open an existing excel sheet that contains an ActiveX control.
Click the button and nothing happens (macro does not launch)
Investigation shows that the button name has changed from "BtnMacroLaunch" to "CommandButton3"
I open the file on other users machines and the button has NOT been renamed and it works correctly.
Environment:
The sheets that have this were last saved on another users machines, not mine. When I save a new spreadsheet with an ActiveX, this does not happen.
If another users opens and executes a sheet I created, then saves that sheet, when I open it again, the button is renamed
This has been a problem since mid Dec 2014 (approx). - which is why I think it is related to the common ActiveX issue.
The majority of my office coworkers (I think everyone but me) had the Dec Update done in Dec. My updates were turned off inadvertently by our IT department. All my coworkers also did the delete "forms.exd" workaround.
I suspected that since my machine had not gotten the updates, that was the cause of the issue. However, yesterday (Jan 19) I finally got my machine fixed and all the updates applied. I then did the the delete "forms.exd" workaround. Unfortunately, the buttons are still renaming.
This does not appear to be exactly the same as the other button rename problem. This is not appending a number to the back of a name, but resetting the name compeletly.
**
**
How do is stop MS Excel from renaming the ActiveX button name? Additionally, is there something that needs to be addressed within our office?
Update:
First: Let me formally state the question(s): How do is stop MS Excel from renaming the ActiveX button name? Additionally, is there something that needs to be addressed within our office?
Second: My company has a support agreement with Microsoft. Finally wound through our internal IT process to get that help.
According to Microsoft, the problem does stem from the December 2014 ActiveX update. The date of that update was 12/9/2014. The associated KBs are KB2553154 for office 2010 and KB2726958 for office 2013. If all the machines that are sharing documents that contain ActiveX controls are not in the same state regarding the KB updates mentioned above, then this problem will occur. So if you have it and they don't there is a problem. If they have it and you don't there is a problem. We have tested this on a handful of machines and getting everyone in sync regarding the KB seems to resolve it.
Why it didn't "resolve" when I got the updates in January. Evidently I did NOT get all the updates in January. Our IT department pushes updates via Symantec Management Agent, there is a breakdown in that process that they are now investigating.
Third: To person that stating I didn't properly ask a question. While I technically have no qualms with your observation, I agree with JLee "If a person reads this problem description and doesn't know the question, that person's comments are not needed anyway". I additionally find it interesting that someone who is that obsessive about posting etiquette would use undefined acronyms such as "OP" - which I had to look up since I do not use forum's extensively.
Ask user to copy the sheet containing the code into another workbook, rename the sheet in the original workbook & copy the sheet back into the original workbook... its a temporary workaround...
