This gave me a clue, and I THINK I have a workround that actually works Otherwise it runs fine without creating ghost sheets # Gareth's (on May 17, 2017) said this in his Edit It only happens if I have the VBA window open. I've seen the bug on other people's systems with later editions of Office too. I know this is a really old thread, but people are STILL having issues, including me, On the plus side, I may have a workaround for my problem. Otherwise it runs fine without creating ghost sheets. It only happens if I have the VBA window open.

Unfortunately I can't seem to find a close method in the VBE to try and kill the object that way.Įdit: it got weirder. When I poke around with the VBE (add a reference to Microsoft Visual Basic for Applications Extensibility, then 'for each in ', I can see that the phantom VBA Project has no filepath, and it's 'BuildFileName' Does that match anyone else's experience? I suspect the problem might be that I'm passing the sheet as an object between different functions. The odd thing is that it's not all the sheets I open, just the ones I'm creating (then renaming) mid-process. I really need a fix, as excel starts throwing 'out of memory' errors if too many of these phantoms stick around, and this process is meant to run continuously. I've got it happening in a process I'm running (reformatting input sheets from various sources). Google desktop wasn't the issue but another program which must also use some. I may well have found an answer to this now here I'm unsure if both these issues are linked however.Īny help or advice that you have would be appreciated (or from any other posters who have seen this issue.) Now runs out of memory and I have to crash out. In some ways I'm unconcerned, however this does seem to hog a bit of memory and sometime excel I've only just started using Excel2007 (not 2010 as in the inital query) and this has started to happen, but when using excel 2003 these issues do not occur.

If I expand the folders under this VBAproject and double click 'thisworkbook' then the info in the properties window is blank which I guess makes sense given the workbook is closed, nevertheless I can still expand and view the modules and all code within ie it's not just add-ins and hidden workbooks that are seen here. In my case if I open an excel workbook with a VBA project and then subsequently close that workbook (but keepingĮxcel open) then the left hand side of the vba project will still hold the info and modules for the now closed workbook. You may well have answered the query that Petra had, but I read the query slightly differently and it matches an error I've been having.

Excel vba on open