VBA by itself renaming "ThisWorkbook" as one of the codesheet's name?

[Muir2014]

For some reason Excel VBA is renaming ThisWorkbook as one of the CodeSheets' name contained within the workbook :

I'm having a hiccup that I haven't find the solution, originally one of the CodeSheet name was --> "ShMC", then VBA changed it to ShMC1 and the "ThisWorkbooK" was renamed as "ShMC".
There are no events in this sheet other than "clicks" events, none of then are named as "ShMC", and no procedure is named as "ShMC".

I have a copy of the workbook, and don't know if at sometime I had both workbooks opened at the same time, and maybe this is the cause.

I need guidance in this matter, and thanks in advanced.

 

[Jeffrey Mahoney]

I have been through this many times and have to fix it many times. The real problem is that the sheet is on the New codename and the VBA code is on the Thisworkbook version

Let me find a link to where I posted the Solution

 

[Jeffrey Mahoney]

Sheet in VBAProject gets copied and converted into ThisWorkbook

Simple answer to fix:

Save a version to .xlsx
Close and reopen
Save as .xlsm
Copy all the VBA code back into the sheets and import the modules

 

[Jeffrey Mahoney]

The problem seems to come back it the file remains as .xslm. I have taken a huge amount of time trying to figure out what causes it. I originally thought it was Excel Tables. I think it is very complex and large sheets.

*.xlsb files don't get the problem

 

[Muir2014]

The problem seems to come back it the file remains as .xslm. I have taken a huge amount of time trying to figure out what causes it. I originally thought it was Excel Tables. I think it is very complex and large sheets.

*.xlsb files don't get the problem

Hi Jeffrey, I had this problem in the past and I couldn't remember what did I do about it, I just remember I never found the cause, I think I did what you suggested as saving as xlsx, then as xlsm, I'll try that again, thanks a bunch!!