Problem with Help file in VBE

  • Thread starter Thread starter 38N90W
  • Start date Start date
3

38N90W

Windows XP Pro
Excel 2002

There are no discs or Media to be had. None. And quite frankly, I don't
know that there ever were.

Anyway, my regular Excel Help works just fine, but the Help for VBA in the
VBE is NOT fine. If while in the VBE I click on the Help menu and choose
"Microsoft Visual Basic Help", the help window shows up just fine. However,
the "Answer Wizard" and "Index" tabs are not accessible. Hovering my mouse
over either of those pages when the tabs are selected results in my mouse
pointer changing from a normal mouse arrow in a horizontal black arrow with
arrow pointers on each end. The "Contents" tab works but only gives me help
on VB, not on the Excel part of VBA.

So, without install or recovery discs am I screwed? I've searched the Net
to no avail. Any help greatly appreciated.

-gk-


========================================================================
"The creative act is not the province of remote oracles or rarefied
geniuses but a transparent process that is open to everyone."
-Greg Kot in Wilco Learning How To Die-
 
Here is a previous suggestion from David McRitchie

Try the following:
Bring up the Windows Task Manager and within the Processes tab,
select msohelp.exe then use the End Process button.
Bring up HELP again.


--

HTH

Bob Phillips
... looking out across Poole Harbour to the Purbecks
(remove nothere from the email address if mailing direct)
 
No luck. After closing the msohelp.exe, I get an error message in the
regular Excel environment, and in VBE nothing happens. If I close Excel
completely and re-open, then the regular help works fine, but the VBE help
is still crippled.

-gk-
 
gk,
Anyway, my regular Excel Help works just fine, but the Help for VBA in the
VBE is NOT fine. If while in the VBE I click on the Help menu and choose
"Microsoft Visual Basic Help", the help window shows up just fine. However,
the "Answer Wizard" and "Index" tabs are not accessible.

There's an article in the Microsoft Knowledge Base that may be
describing the problem you're having. See:

http://support.microsoft.com/?kbid=319956
 
Back
Top