>David,
>
>I just tried a test form and the context sensitive help worked just as advertised.
>
>Hmmm, maybe the framework has used ON KEY to somehow change the F1 key to always bring up the help contents. I guess I'll have to do some digging. Thanks again for your help.
>
>- Mark
>
>>Mark,
>>
>>It sounds as though SET HELP is not set to your help file. You do not need to set individual controls unless you want them to display their own topic. If a control does not have a HelpContextID VFP will send the HCID of the form to the help engine.
>>
>>>Well, I tried setting the form's HelpContextId to 16. When that didn't work, I did a select all in design mode and set everyone's HelpContextId to 16. When that didn't work I tried setting the WhatsThisHelpId to 16 as well.
>>>
>>>For some reason, the form is passing the context ID 1879048194 to the help engine instead of 16 (even though the form's help context id is 16). I'm stumped.

My short experience is that HelpContextID's work fine from VFP6, provided that you specifically set helpto a file named .CHM which is on the VFP path. Set topic does not work in VFP6.

I suspect your problems might be in the help file itself, and you need to download v1.2 of the htmlhelp workshop to figure it out from the rather inadequate help file that comes with it.

The sections of the html help you generate need symbolic ID= Statements , something like ID=IDH_1001 (can be any name, but I think that using what will be your helpcontextid makes it easier to keep track of). Then in the help project you need to include a .h file (eg, MYHELP.H). This contains statements like

#define IDH_1001 1001 (one for each context id you wish to use)

These equate the numeric id's with the help content in the html file.

Include this file in the project, and compile it to get the .CHM, and you are on your way.

Geoff