S
SidBord
I run Office11 (2003) under Win XP on a Dell 8300 with 512 Mb.
I run Spybot, Ad-aware, Norton Internet Security & AntiVirus.
I keep them all updated. I recently installed Office Sp1.
That said, for the past 3 weeks I've been averaging 7 Excel
crashes a day, which Event Viewer blames on VBE6.Dll. I
renamed that program and ran Excel Detect & Repair, and it
did indeed replace VBE6.dll. I tend to have crashes in
workbooks that do (or used to do) event processing. They
all reference Personal.xls to get certain macros I've
written. All these workbooks are at least 2 years old
running essentially the same macros, all of which I have
written. I've had a hard time trying to find out what's
common in the failures. The most recent ones are all
recovered automatically with the comment "No repairs done.
None were necessary". I can usually go into the main
executing macro and step through it successfully, then the
workbook operates OK. It might operate OK the next time,
but it isn't long before it will crash again. On two
occasions I tracked the error to incidents in which the
macro was attempting to execute another macro resident in
Personal.xls. Those macros have all worked great for a
long time. I'm not even sure the called macro ever starts
to execute. It's almost as though the call triggers the
crash. I thought at first it was my event processing
(Workbook_Open and Workbook_SheetChange) that was the
problem, so I cut back or in some cases cut out their use.
Now I'm not so sure events are the problem, because once
I get the macro working, it will continue to work if I use
it repeatedly. However, later in the day the workbook
might crash. I haven't found anything relevant in the
Knowledge archives. Lots of stuff for Word 2000. Yes, I
know that it's common at this point to say reinstall Excel
or Office. That's a massive job which I am almost sure to
screw up, and I've read too many places where people have
done that and it didn't help. I still haven't been able
to determine just what VBE6.dll does for a living. It's
obviously connected in some way with Visual Basic.
Comments anyone??
I run Spybot, Ad-aware, Norton Internet Security & AntiVirus.
I keep them all updated. I recently installed Office Sp1.
That said, for the past 3 weeks I've been averaging 7 Excel
crashes a day, which Event Viewer blames on VBE6.Dll. I
renamed that program and ran Excel Detect & Repair, and it
did indeed replace VBE6.dll. I tend to have crashes in
workbooks that do (or used to do) event processing. They
all reference Personal.xls to get certain macros I've
written. All these workbooks are at least 2 years old
running essentially the same macros, all of which I have
written. I've had a hard time trying to find out what's
common in the failures. The most recent ones are all
recovered automatically with the comment "No repairs done.
None were necessary". I can usually go into the main
executing macro and step through it successfully, then the
workbook operates OK. It might operate OK the next time,
but it isn't long before it will crash again. On two
occasions I tracked the error to incidents in which the
macro was attempting to execute another macro resident in
Personal.xls. Those macros have all worked great for a
long time. I'm not even sure the called macro ever starts
to execute. It's almost as though the call triggers the
crash. I thought at first it was my event processing
(Workbook_Open and Workbook_SheetChange) that was the
problem, so I cut back or in some cases cut out their use.
Now I'm not so sure events are the problem, because once
I get the macro working, it will continue to work if I use
it repeatedly. However, later in the day the workbook
might crash. I haven't found anything relevant in the
Knowledge archives. Lots of stuff for Word 2000. Yes, I
know that it's common at this point to say reinstall Excel
or Office. That's a massive job which I am almost sure to
screw up, and I've read too many places where people have
done that and it didn't help. I still haven't been able
to determine just what VBE6.dll does for a living. It's
obviously connected in some way with Visual Basic.
Comments anyone??