I get it. You are right, its the Foxhhelp.exe file and/or the Foxhhelpps.dll files. We do have them loaded on the individual machines and I (now remember) that I did check the fox html help for the setup that loads the runtime on the users machine.

The problem is the runtime and related files are not loaded on the server that launches the applications. We run all our apps from the client even though the apps live on another server. So in essences, help can not load because its root does not have the necessary dll's, right.

Sergy's reference to the knowledgebase really helped register what was happening.
Thanks you both for the wake up.

>In order for help to work, there needs to be a DLL (I don't remeber its name, probably foxhelp.dll) installed on the client machine. Just like the VFP runtime files need to be. The setup wizard takes care of this. If you don't use a setup program, then you will need to find a way to copy (and probably register) this DLL in the client computer yourself.
>
>BTW, the reason it works on your development machine is becaue when you installed VFP on your computer, the VFP setup program installed this DLL in your computer.
>
>>Hector
>>I am not using a setup program. I created a desktop shortcut to the exe and the chm help will not display when F1 use pressed or the button is clicked.
>>
>>>When you create the setup program for your application, make sure you check the "HTML Help" option (or something like that) in the setup wizard.
>>>
>>>