VBA Project not closing after closing Excel file

[GOGGS]

Hi

I have been having a problem since upgrading to Excel 2016 I'm hoping someone can help with. The problem is that after closing a file with a macro built in the macro still exists when looking at the VBA Editor although the Excel file is closed. This causes Excel to crash when working on the next spreadsheet I open. I have been avoiding the crash by always exiting Excel after closing a file with a macro built in then re-opening it but I am trying to solve the bug.

I have already taken various actions after surfing the web without success. The actions being as follows:

Disabled the only COM add-in that was enabled.
Checked a Personel.xlsb file did not exist after reading that this should be deleted
Deleted the Ribbon and allowed this to be recreated automatically in case it was corrupt.

Does anyone have any other suggestions?

Thanks

[AlphaFrog]

1. Can you open the workbook but not run the macro and then close the workbook; does the macro still persist?
2. Is the macro using Application.OnTime?
3. In the code, are you calling a library?
4. What does the macro do?
5. Can you show the code?

[jaslake]

Hi GOGGS

Is the Macro File an xla or xlam File (Excel Add-In)?

[GOGGS]

Hi

The macros are all on xlsm files. I carried out a simple test that cancels out a number of possibilities. I created a new one line macro on a
new xlsm file. This executing the command MSGBOX. I then saved the file and 'closed' it. I opened a new file and the macro was still visible in
the VBA editor. It is no longer available to run via the 'Developer' tab on the ribbon but can be selected in the VBE editor and stepped into?

Thanks for any help.

[GOGGS]

Hi

I noticed another mystery when testing that may indicate what is causing the problem. The references box on the VBA editor refers to the file that has been closed without successfully closing the VBA Editor. See below:

box.JPG