My usual way of solving issues of odd behaviour of this sort is to:
• Quit all Microsoft programs
<snip>
• Re-launch the troublesome program (Excel, in this case).
When I was training Microsoft Support Engineers back in the mid-90's, that was essentially the standard first response "
fix" we taught regardless of whether it was on a Windows or Mac platform. I could go on at length into the reasons why this is still the case with their products but it is still the standard first response "
fix" for Windows and Windows apps.
Apple is not perfect, but at least they had the good sense to admit when the code base for their OS and apps was not worth trying to "fix" and they started over with a clean sheet of paper. I suspect there are those at Microsoft who wish it were economically and politically feasible for them to do the same. In that sense they are held captive by their own market dominance.
