I have had this happen several times before and always ended up rebuilding the entire workbook.
The problem hit me today it is inside a pretty big workbook with vba code that was not working correctly.
I tried several dozen "fixes" but eventually had to bite the bullet and rebuild it. After rebuilding it the vba worked properly.
But in my efforts to fix things I came up two interesting workbooks.
Open NoBug.xlsm an run sub deletenow33. It does not abort.
Open Bug.xlsm and run sub deletenow33. You will see an abort.
The Workbooks are practically identical except Bug.xlsm gives the privacy warning.
I have virtually everything including reverting from xlsm back to xls, and the bug still occurs.
I am considering turning the .xlsm into a .zip file and doing further research, but I hope someone on experts exchange can tell me how to fix the problem WITHOUT rebuilding the workbooks.
a very simple example of why this problem is so frustrating.
I have attached to workbooks Bug.xlsm and NoBug.xlsm. They are nearly identical. The only difference is that when I save the first