David,

Perhaps I didn't explain my problem well enough. The question is, how to modify FPW code to that context-sensitive help working when the code is run in VFP as well as in FPW. Since we are running FPW code in VFP, there are no form objects and form properties to set. So setting the Form.HelpContextID doesn't apply.

I would like to put the topic ID setting code in a single UDF. Where should the UDF be invoked? I could add a procedure call, something like "do SetHelpID with ''", to the activate snippet of each screen. But I'm trying to avoid having to modify all my FPW screens. Is there any way to handle this globally?

Perhaps I could program the F1 function key ("ON KEY LABEL F1 DO SetHelpID") to call the UDF. But then how does the UDF know which SPR we are in? I don't know any way to get the title of the current screen. Perhaps I could use FoxPro's PROGRAM() function to get the name of the SPR, then do a lookup in a table to get the topic ID. Do you know of a better way?

---Tim


>Tim,
>
>To add a little to Mark's reply. If you only set the Form.HelpContextID all of the controls on the form "inherit" that ContextID. So in your case you shouldn't have to worry about using the control HelpContextIDs. Also this works with true VFP form objects not recompiled SPR code. I'd put the topic id setting code in a udf so the VFP vs FPW code is in only one place.
>

Thomas M. Lamm
Bradbury & Associates