M
Max Moor
Hi All,
I have an Access 2002 application with a compiled HTML help file. In
the Form_Open event code for a number of my forms, I set 'Me.HelpFile' and
'Me.HelpContextId' to point at part of my help file. On my developement
machine, I can open one of these forms, press <F1>, and the help file opens
to the proper page.
The problem is with installations on client machines where I install
Access Runtime (although I doubt this is a runtime issue).
In either case, I can open my help file via the menu bar, which calls
"HTMLHelpStdCall" from hhctrl.ocx. When I press <F1> on a form, however,
nothing happens. The mouse pointer may change to an hourgless for an
instant, but that's it. The help file doesn't open, and there's no error
message. I'm not sure what behind-the-scenes magic happens when trying to
open the file this way.
Since opening from a form in context works on my developement PC, I'm
assuming that the path to the file and the context ID are both valid. (The
path to the file is called out the same whether from the menu or a form.)
So, what could be the problem?
Both my developement PC and my test PC are running Windows XP SP2. I
ship hhctrl.ocx with my package, but XP already has a more up to date
version of that, so doesn't want it anyway.
Can anyone explain the hidden workings of how the forms open a help
file in context, as opposed to how the menu does it? Any thoughts as to
what I might be doing wrong?
Regards,
Max
I have an Access 2002 application with a compiled HTML help file. In
the Form_Open event code for a number of my forms, I set 'Me.HelpFile' and
'Me.HelpContextId' to point at part of my help file. On my developement
machine, I can open one of these forms, press <F1>, and the help file opens
to the proper page.
The problem is with installations on client machines where I install
Access Runtime (although I doubt this is a runtime issue).
In either case, I can open my help file via the menu bar, which calls
"HTMLHelpStdCall" from hhctrl.ocx. When I press <F1> on a form, however,
nothing happens. The mouse pointer may change to an hourgless for an
instant, but that's it. The help file doesn't open, and there's no error
message. I'm not sure what behind-the-scenes magic happens when trying to
open the file this way.
Since opening from a form in context works on my developement PC, I'm
assuming that the path to the file and the context ID are both valid. (The
path to the file is called out the same whether from the menu or a form.)
So, what could be the problem?
Both my developement PC and my test PC are running Windows XP SP2. I
ship hhctrl.ocx with my package, but XP already has a more up to date
version of that, so doesn't want it anyway.
Can anyone explain the hidden workings of how the forms open a help
file in context, as opposed to how the menu does it? Any thoughts as to
what I might be doing wrong?
Regards,
Max