We found the same issue with 2008 RDP. We've done two things. Confirm the the user has access to the two files foxhhelp9.exe and foxhhelpps9.dll. Then instead of calling HELP we're calling HELP ID and this brings up the help for a specific page (we use a default ID within the help file). We also make use of the WhatsThisMode method.

Hope this helps
Jon

>>>Did you try to open help file from Windows Explorer?
>>>
>>>>We have an application which for years has been running on hundreds of desktops. Included with that app is a help file which is typically activated from the Menu (cmd Help). When this same system is run from an RDP session (W2008) the help command no longer works..
>>>>
>>>>Has anyone experienced this, and can anyone offer a fix?
>>>>
>>Hi Sergey,
>>
>>Yes it does work when executed from Windows Explorer. In the meantime I am now using the following:
>>run /n hh.exe somehelpfile.chm
>>
>>While this technique works the VFP command "Help" refuses to work.
>
>Once upon a time, in FPD2.6, I used
>
>on key label f1 do MyHelp
>
>and there I checked a few things to get the context and somehow managed to find where was it called from, so I had context sensitive help. I sometimes even had html file with hierarchical navigation, so where that was available (i.e. running FPD on a windows machine), I'd launch the browser with appropriate link into the local file; if not, I'd do a Set Topic To and call the usual dbf help.
>
>Nowadays, to get the context you'd probably check the active form and its active control.