Excel : VBA: Corrupted Command Button

[TMS]

I would appreciate any thoughts or insight you might have into this scenario.

I developed a workbook for a client a couple of years ago. All has been working fine until he recently opened the workbook and discovered the command buttons don't work. Not the obvious macros not enabled or Event handling switched off.

He sent a copy over to me and, sure enough, they don't work. On investigation, I typed the button name, btnSetup, into the name box ... and it selects an apparently blank button. I can check its parameters and I can delete it but that seems about all. The button itself is still present but, seemingly, now separated somehow. And the code for the command button click Event is still there. So, everything is present but now split into component unlinked parts.

I can fix the problem but I am intrigued as to the cause ... and if there is a remedy.

As it stands, I will copy the command button from an old copy of the workbook, rename it and link it to its code. Think that works (will test later).

In the meantime, any thoughts, ideas, suggestions or solutions.

Thanks, TMS

[xlnitwit]

Hi,

If the buttons are ActiveX, I would suspect the recent Office updates which changed the fm20.dll and caused numerous bugs with userforms. If you can, I would very much recommend replacing them with Form controls.

[TMS]

Thinking about it, I can probably just recreate the button from scratch.

@xlnitwit: thanks for the suggestion. No reason why not. The click Event just calls a subroutine in a standard module. Do you have any documentation, references or specific knowledge base entries and dates for the problem.

Thanks for the quick reply

[xlnitwit]

This is the only official support response I have seen besides a few MS posts to questions in Answers or Technet- https://support.office.com/en-us/art...ad=US&fromAR=1

Here is one of the Answers posts as well- https://answers.microsoft.com/en-us/...d-b088bc131411

It doesn't specifically mention MSForms controls on a worksheet, but it would seem to me to be a large coincidence for the two to be unrelated. I also recall there was a similar issue a couple of years ago with an Office update that rendered all activex controls on worksheets useless- and there were others many years ago- which is why I do my level best to avoid them.