Excel Macro Command Button Not Working

Question

Hi everyone,

I have a user who is unable to click command buttons in Excel sheets, but these same buttons work for other people.

When clicking the button a "ghost" of that button will appear in some location around it, and if that ghost intersects with the original button it can be clicked and the macro will run. See below for an example screenshot.

This user can run the macro manually, or with an associated keyboard shortcut, it is just the command buttons that do not work. We created a test worksheet on the user's machine and the macro button will not work, but sending the same file to my machine the button will work.

I have tried an online Office repair, checked macros are enabled, compared settings to my own but nothing seems out of place.

Any assistance with this would be much appreciated!

Answer 1

I have the same issue. There appears to be a bug. I read in another forum that if you use a docking stations (as I do), I should remove my laptop from the dock and try again. Low and behold the buttons worked again. [I redocked and they are currently still working]. 

MSFT can you please address this bug. 

[Edit] .  Okay, once redocked buttons fail to work again. - Current (unexceptable) solution, only access files with command buttons 'undocked'.

Answer 2

If you are using Windows 10 and Office 365, try allowing Windows to fix blurry apps:

https://support.microsoft.com/en-us/help/4091364/windows-10-fix-blurry-apps

Answer 3

Sam_Vickers:  Were you able to figure out a solution.  I have the exact same problem, my tech support has reload/repaired office 365, six times now, but at least I'm not losing my mind :) .  I am the only one having the issue, so no one has been able to figure it out.

Thanks, Brad  

Note:  After reading merlin's comment below I'm wondering...I dont have a docking station but am using 2 external monitors.

Answer 4

I am having the same issues at MerlinJnr since the last Office update.  It doesn't work with docking and does independently.  I also have 2 monitors and it does not work, when docked, on either monitor.  Any new ideas?

Answer 5

The text 'CommandButton1' in the original post suggests to me that Sam (maybe others?) might be using an ActiveX button instead of a Forms button (which I'd expect to have the default label of "Button 1"). I'd suggest trying a forms button, and testing with the same user(s) to see if that avoids the problem.

I gave up using all ActiveX controls in my projects years ago because of how squirrely they are, especially when trying to deploy and maintain over multiple end users (all with machines with slightly different configurations). My issues were more around functionality and unexpected machine crashes, so your mileage may vary...

Just something worth trying, since it looks like this thread has been open a while and keeps getting new hits. If the folks on this thread reply saying they are also experiencing the same issue with forms buttons, then I'm out of ideas...