Problems with Office Help files (2000 and XP!)

[Peter]

Hi all
Some strange things as happened to the help in Office 2000
and Office XP.
If I hit F1 in theVBA editor the links in the help window
does not work. It's supposed to show "See
also", "Properties", "Methods", "Events" etc. depending on
the help context Office is showing! But the "links" seems
to be broken!
See what it looks like here :
http://www.forsbom.com/vbahelp.jpg

My company is using Office 2000, and this problem started
about a moth ago, and is affecting ALL users!!
The company is going to upgrade to Office XP November 3.
and I am testing it out. We were hoping that the problem
would disappear when we upgraded but it's still there !!!!

I would really appreciate any input on this matter!!

By the way...
Not all the links have disappeared, but they just give me
an error message:
See what it looks like here :
http://www.forsbom.com/vbahelperror.jpg


Best regards
Peter

 

[Pete Lees]

Peter,

Some strange things as happened to the help in Office 2000
and Office XP.
If I hit F1 in theVBA editor the links in the help window
does not work. It's supposed to show "See
also", "Properties", "Methods", "Events" etc. depending on
the help context Office is showing! But the "links" seems
to be broken!

This problem is described in Microsoft Knowledge Base article 822989
(http://support.microsoft.com/?kbid=822989). Unless you've installed
Service Pack 4 for Windows 2000, the solution should be to apply
Critical Update 811630, which is available from here:

http://support.microsoft.com/?kbid=811630

I'm starting to see reports that installing Windows 2000 SP4 *causes*
this problem. If you're a Windows 2000 user and you have installed
SP4, the solution is first to run this command from a command prompt:

regsvr32 /u <drive>:/winnt/system32/hhctrl.ocx

and then run this command:

regsvr32 <drive>:/winnt/system32/hhctrl.ocx

The first command unregisters the HTML Help ActiveX control, which is
what provides the navigation features in the help files; the second
command re-registers the control. This should fix the broken registry
entries that are responsible for the problem.

 

[Peter]

Tanks a LOT !!! I'll look in to as soon as I get to work !


Peter