View Single Post
  #10  
Old September 8th, 2004, 07:37 PM
nikbottom
external usenet poster
 
Posts: n/a
Default

I'm actually almost leaning towards the possibility of it being an Office
update of some kind. All of my PC's should be at the same patch level since
we have group policy mandating they update Windows patches daily. We don't
yet have that in place for Office 2003. People can update at will and we
only have a handful out of several hundred machines experiencing the issue.

At least only a handful of users have complained.

"Paul E. Jones" wrote:

So, it would appear that a recent Microsoft update has introduced this
problem. I, too, had been running with the exact same configuration for
some time. This file is one I edit several times each week and had even
edited it during the day prior to updating to SP2. I never had this problem
until I installed SP2.

You're indicating that you have been running with the same config and it
just recently started happening. You're running Windows 2000, so I would
guess that security updates were probably released more gradually than XP,
since SP2 was forthcoming.

The only conclusion I can draw is that Microsoft changed something recent
security updates. Our anti-virus programs are different, so we can't blame
those (and disabling them had no impact, anyway).

Paul


"nikbottom" wrote in message
...
I too am experiencing the same issue with Windows 2000 Machines running
Excel
2003. I have also tried disabling Virus scan (McAfee) with the same
result.
This just started a couple of weeks ago, but we have been running 2003 for
several months now. Any more ideas would be appreciated.