Tim,
I've not touched FPW in several years now, so I'm way rusty on it's specific issues. I did port raw FPW code into VFP to get around the fast machine problem for one client, we did no app functional changes though, only the minimum mods to get it running.
You might use an OKL and test WONTOP() or maybe PROGRAM() and embed all of your help topic setting in one routine instead of changing every screen or use a table lookup as you thought.
Are you trying to stay with FPW to build screens from the screen builder? I think you'd have to put code in the screen setup that would call the UDF. You can use macro expansion to get around compiling code that FPW doesn't understand.
>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?
