In the process of investigating whether I had a proper vshelp.dll file, I
found something interesting.

System is a multiboot system, with a different Office in each boot system.

Using windoze explorer, I did a search for vshelp.dll,
A copy was found on the C and F drives, but none on the G and J drives.
So I manually looked for the file on the G and J drives. Files are present.

So, one bug is that windoze explorer missed listing the files in the Search
on the G and J drives.

Office 2003 is in the OS on the J drive.

I searched thru the registry and found that vshelp.dll was already
registered on the J drive, but I ran regsvr32 anyway.
The F1/Help problem continues.

MSFT needs to issue a fix, not tell us to do tumblesaults as in KB article
216109.

MSFT has greatly improved the functionality, performance and ease of use in
Office over the years, but they still need to get their act together on
installation issues.

--
http://www.standards.com/; See Howard Kaikow's web site.
"Jezebel" wrote in message
...

"Howard Kaikow" wrote in message
...
My account is part of the Administrator group, so that should not be the
problem.

Rather than creating shortcuts, I start an instance of Word/Excel, in
addition to the VB 6 design window.
But this is a crock that MSFT needs to fix ASAP.


You're right, but I wouldn't hold your breath.