Forum Discussion
Multiple *.xlsm files no longer recognize attached VBA modules and files are uneditable/unsaveable.
This began with Excel 365 version 2307 some months ago, and got considerably worse with version 2312. It used to be two or three times a week, but now it is happening three or four times daily. Bef...
peiyezhu I am already exporting the modules as *.bas and have already doubly backed up some as text. The problem is that the *.xlsm file is now useless (un-repairable). I am losing one to three files DAILY and have to TRY to re-enter all of the data I lost since the last save. Some of the larger files I am backing up to *.xlsx then importing the *.bas and resaving as *.xlsm (but even that does not work all of the time as the "new" *.xlsm opens as un-editable/un-repairable.
P.S. It's not as if I am changing the VBA code, some of these files have worked faithfully for years, some are new with new codes. I have even tried copy/paste from a backup into a new blank file, but Office 365 appears to hate *.xlsm on Windows 10 (and no, I cannot update to 11 yet until the company does (probably in 2025).