Duplicate Projects in VBE project Window... Very annoying.

[MikeZz]

I've been having issues with the VBE project window.
When I first open excel VBE, it's pretty clean.
But if I open a file, then close it, the VBE project does not close.
Then if I reopen the same file, I have 2 identical projects open.

Is there a setting that will close the VBE project when the excel file is
closed?

It's getting to the point where I don't know which one to work in and I've
lost Hours of work because I saved what I thought was the right file but for
some reason it didn't save the VBE code to the excel file. It must have
saved it to the phantom file which must not have existed.

Thanks for the help!

 

[Dave Peterson]

There have been a few theories about what causes these phantom projects--but
I've only seen one way that removes them--close excel and reopen it.

This may be the best approach if you think you may be confused and lose work.

 

[Alan]

You might try this free utility. I found it when I started having strange
things happen after running code with the debugger.

http://www.appspro.com/Utilities/CodeCleaner.htm

"During the process of creating VBA programs a lot of junk code builds up in
your files. If you don't clean your files periodically you will begin to
experience strange problems caused by this extra baggage. Cleaning a project
involves exporting the contents of all its VBComponents to text files,
deleting the components and then importing the components back from the text
files."


Regards,

Alan

 

[Jon Peltier]

I had this problem a few months ago, and when I uninstalled a program that
accessed Excel via VSTO, the phantom VB Projects disappeared. I read more
recently that another user solved his problem by removing a different VSTO
program. To me, it seems obvious that VSTO is the culprit, and I think
that's what you should look for.

- Jon

 

[MikeZz]

THis is probably a dumb question but what's a VSTO?

 

[Jon Peltier]

If VBA isn't fancy enough for you and you want to feel like a real developer
and use dot-net and all, then you can use VSTO, or Visual Studio Tools for
Office. It's an infrastructure to develop within which allows dot net to
control Office applications. This takes a simple rapidly developed VBA
add-in, slows its development cycle, and adds all that overhead to your
project. I'm being a bit facetious, of course, but maybe not entirely.

- Jon