[MeistersingerVonNurnberg]

Hi All -

Really cannot say for sure what is happening here. I have a pretty robust
6500 line macro in Excel VBA. It's worked for years; a very tight Excel VBA
app that has been thoroughly tested. No other add-ins. No forms. Takes data
from one sheet, and produces bar charts essentially in another sheet. No
graphical objects, just formats cells and stuff. I had a SelfCert certificate
attached to it. I removed the certificate so I could edit the macro in
development mode recently.

Other workbooks in the same folder I am working are giving "locked for
editing by" messages when I try to open them. Some of the workbooks I have
opened while I was editing my robust macro in the VBE. Some of the workbooks
I launched by "enabling macros" while I was in the VBE editing the robust
macro. Some of the workbooks I have actually physically changed the file name
of, and then when opening for the first time with the new file name, I get
the message.

I was having this problem this afternoon, changed the name of my working
folder. Rebooted, and seemed fine. Changed the folder name back, still seemed
fine. Did some hours after drinks tonight, and the problem is back.

Now, functionally speaking, if I get my robust XL app, or any of the others
I am referencing while developing, to open properly, everything works as
expected. No functional flaws at all. Just XL thinks the file and some of its
friends are open when they are not.

Only system change was MS security updates for January that came in last
week or so, and the McAfee ones that came right behind it.

Any ideas?