VBAProjects still visible after workbook has closed
 

Has anyone ever had the problem that even after you close a workbook,
its VBProject is still visible (and editable - although not savable)?
It is annoying because sometimes I have like 5 VBProjeects open in
addition to all of my add-ins, and the space gets very cluttered.

Also, it is strange.

I can't really give an example on how to reproduce this error, because
it seems to happen randomly. It has nothing to do with reference
problems because even workbooks that I create for a simple task and save
and close within 5 minutes (without ever referencing it at all from
anywhere else), persist in the VBE.

Any help would be appreciated.

VBAProjects still visible after workbook has closed
 

What do the macros do? Which version of Excel?


"R Avery" wrote in message
...
Has anyone ever had the problem that even after you close a workbook,
its VBProject is still visible (and editable - although not savable)?
It is annoying because sometimes I have like 5 VBProjeects open in
addition to all of my add-ins, and the space gets very cluttered.

Also, it is strange.

I can't really give an example on how to reproduce this error, because
it seems to happen randomly. It has nothing to do with reference
problems because even workbooks that I create for a simple task and save
and close within 5 minutes (without ever referencing it at all from
anywhere else), persist in the VBE.

Any help would be appreciated.