WINXP, SP2
XLXP, SP3

Has anyone else seen a certain file shown in the VBAProject Browser multiple
times or even files that's currently not open as showing in the VBAProject
Browser?

If so, what is the resolution to resolve this sort of issue cause I don't
like the looks of this behavior, and suspect this is what's eating up my RAM
usage. I have only started noticing this behavior when I started using
range names (User Defined Names), but yet, I like to use range names to
prevent other types of issues that's caused when changes are taking place.

--

Sincerely,

Ronald R. Dodge, Jr.
Master MOUS 2000

A year or two ago, this was attributed to the Google desktop search utility,
but I understand that they've fixed that.

More recently I've had the problem on my computer after installing VSTO/.Net
add-ins. Apparently if resources aren't properly accounted for (please don't
ask me the details!), you get VBProjects that don't close. These VBProjects
that remain open are unrelated to the faulty add-ins. The developers of the
add-ins I had problems with have supposedly fixed this problem, so it can be
fixed.

- Jon
-------
Jon Peltier, Microsoft Excel MVP
Tutorials and Custom Solutions
http://PeltierTech.com
_______


"Ronald Dodge" wrote in message
...
WINXP, SP2
XLXP, SP3

Has anyone else seen a certain file shown in the VBAProject Browser
multiple times or even files that's currently not open as showing in the
VBAProject Browser?

If so, what is the resolution to resolve this sort of issue cause I don't
like the looks of this behavior, and suspect this is what's eating up my
RAM usage. I have only started noticing this behavior when I started
using range names (User Defined Names), but yet, I like to use range names
to prevent other types of issues that's caused when changes are taking
place.

--

Sincerely,

Ronald R. Dodge, Jr.
Master MOUS 2000

Thank you for the update. My system was reimaged almost 2 months ago and it
went from Windows 2000 to Windows XP, which I wasn't having any major
problems using Windows 2000 Pro, but did run into various issues using
Windows XP Pro. The only reason why my system was reimaged, when I ran the
AI Daylight savings patch on the system, it caused the system to go into a
constant rebooting cycle. The mistake was the IT person that created the AI
file didn't notify anyone that it was only to be used on WinXP, and I got
hit by that fact. I lost a lot of settings and other things. I'm still
having to put things back onto my system cause of that complete restore
process, though going from W2K Pro to WXP Pro.

That took place as I was going from auditing my production reporting system
cause of the various changes that took place to the point that it caused my
numbers to go out of alignment to the point of putting in various things to
minimize that impact and along the way, that's when I ran into this issue.

I shall update further on this issue to give an indication of what needed to
be done to prevent this sort of behaviour in the future. Of course, that
also means I have to find a consistent pattern to this issue too. The main
reason why I got into this line of work is cause I didn't want to do data
entry for a living, especially given the CTS issue that I had when I worked
at the IRS and the IRS breaking their own manual's policy on how to
administer breaks for those in the data transcribing department. While
90%-95% of what I learned is self taught, it's what allowed me to advance as
much as I have, which avoiding that constant data entry by programming as
much of that data entry as possible to be done automatically and/or with
checks in place, it's served up a lot of benefits along the way (saving
money, reducing human errors, reducing the health risk of getting CTS,
increased accuracy, and reports on a more timely basis as the main benefits)

Sincerely,

Ronald R. Dodge, Jr.
Master MOUS 2000

"Jon Peltier" wrote in message
...
A year or two ago, this was attributed to the Google desktop search
utility, but I understand that they've fixed that.

More recently I've had the problem on my computer after installing
VSTO/.Net add-ins. Apparently if resources aren't properly accounted for
(please don't ask me the details!), you get VBProjects that don't close.
These VBProjects that remain open are unrelated to the faulty add-ins. The
developers of the add-ins I had problems with have supposedly fixed this
problem, so it can be fixed.

- Jon
-------
Jon Peltier, Microsoft Excel MVP
Tutorials and Custom Solutions
http://PeltierTech.com
_______


"Ronald Dodge" wrote in message
...
WINXP, SP2
XLXP, SP3

Has anyone else seen a certain file shown in the VBAProject Browser
multiple times or even files that's currently not open as showing in the
VBAProject Browser?

If so, what is the resolution to resolve this sort of issue cause I don't
like the looks of this behavior, and suspect this is what's eating up my
RAM usage. I have only started noticing this behavior when I started
using range names (User Defined Names), but yet, I like to use range
names to prevent other types of issues that's caused when changes are
taking place.

--

Sincerely,

Ronald R. Dodge, Jr.
Master MOUS 2000