Red over White
Board Regular
- Joined
- Jul 16, 2011
- Messages
- 132
- Office Version
- 365
- Platform
- MacOS
I have recently upgraded my system to High Sierra only for my XSLM file, which is 3.7 MB in size, to stop saving with the above message. I get this message even if I go in and then try and save the program without changing anything. If I leave the file open, the message comes up following by the auto-recover disabled message.
The problem appears to be macro based, as the list of macros that normally appear in the drop down function is blank. However, I also have shortcuts to some of the macros on my top bar, and these will operate the macros. This means the macros are somewhere within the file. When I go into the Editor function I get the same 'NEM' message. The program was working fine before the upgrade, and smaller files work fine don't get this message and the macros are listed.
I am on Excel 2011 and am aware, through a recent update (put on after the problem appeared), Microsoft stopped supporting this version in October 2017. I am reluctant to move onto 365 until the problem is solved and as the smaller files are working I don't believe the version or the High Sierra elements are a factor.
Any suggestions where I should start looking to fix the problem would be gratefully received.
The problem appears to be macro based, as the list of macros that normally appear in the drop down function is blank. However, I also have shortcuts to some of the macros on my top bar, and these will operate the macros. This means the macros are somewhere within the file. When I go into the Editor function I get the same 'NEM' message. The program was working fine before the upgrade, and smaller files work fine don't get this message and the macros are listed.
I am on Excel 2011 and am aware, through a recent update (put on after the problem appeared), Microsoft stopped supporting this version in October 2017. I am reluctant to move onto 365 until the problem is solved and as the smaller files are working I don't believe the version or the High Sierra elements are a factor.
Any suggestions where I should start looking to fix the problem would be gratefully received.