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.S. ESET anti-virus installed by the company, cannot be turned off.
- How about VBS(visual basic script) instead of VBA?
- I spent some time on it, will be very difficult (Interacts with Internet, Excel files on our company's server, and MS Word), and then I found this... https://learn.microsoft.com/en-us/windows/whats-new/deprecated-features-resources. VBScript won't be around more than a few years.
