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.
>For a number of reasons, we have decided to recompile our FPW2.6 application under VFP. After fixing a few coding problems, the application basically works. However, I am having trouble getting the context-sensitive help to function in VFP.
>
>When our application runs in FPW2.6, if you press F1 you get the help topic for the screen you are on. FPW automatically calls up the help topic with the same name as the title of the screen.
>
>When our application is recompiled and run in VFP5.0, if you press F1 you just get the contents page from the help file.
>
>I have discovered that I can get the correct help topic to display by:
>
>1) Issuing "on key label F1 help" in the application setup code, and
>2) Putting "set topic id to
" in the screen Activate code, where is the context ID for the help topic for the screen.
>
>This code causes an error in FPW, since "set topic id" is VFP-only. I can can around that by conditional compilation. The main problem is that I have to modify every screen to explicitly set the topic id.
>
>Does anyone have a better way to get context-sensitive help to work in a FPW program when it's run under VFP5?
