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
-------
Jon Peltier, Microsoft Excel MVP
Tutorials and Custom Solutions
http://PeltierTech.com
_______


"MikeZz" wrote in message
...
THis is probably a dumb question but what's a VSTO?

"Jon Peltier" wrote:

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
-------
Jon Peltier, Microsoft Excel MVP
Tutorials and Custom Solutions
http://PeltierTech.com
_______


"MikeZz" wrote in message
...
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!