>>Why don't you include those files in the Setup program and do their installation from the Setup?
>>
>>Vlad
>>
>>>On older computers that do not have IE4 or later, this is what I had to do to get HTML Help to work in VFP applications.
>>>
>>>First, download the HHUPD.EXE file from MS. Select the correct language to download.
>>>
>>>I then created a small VFP executable for each user to run. The code is as follows:

>>>set talk off
>>>set safety off
>>>copy file foxhhelp.exe to c:\windows\system\foxhhelp.exe
>>>copy file foxhhelpps.dll to c:\windows\system\foxhhelpps.dll
>>>run /n foxhhelp /regserver
>>>run /n hhupd.exe

>>>
>>>Change the paths above for NT workstations as needed.
>>>
>>>I then place the EXE, foxhhelp.exe, foxhhelpps.dll and an empty foxuser.dbf/fpt file all in the same folder. The foxhhelp files are in the VFP Home() directory. Tell the user to double-click the VFP executable you create from the code above.
>>>
>>>Then in your applications all you have to do is include a line early in your main PRG --
>>>
>>>SET HELP ON
>>>SET HELP TO MYHELP.CHM
>
>This would be ideal, but I am not sure how to duplicate what HHUPD.exe does [does it register anything, etc.] and how to do the foxhhelp /regserver in the setup. Plus, this was a supplemental install after the users had installed the original app. I did not need them to re-run the entire install process. My LAUNCHER.EXE updated the actual APP that runs.
>
>For my next APP and future new installs for existing APPs, I will do some extra digging to see if I can add all of this to the SETUP.

Do you use the vfp setup wizard? If so, does the "HTML Help engine" option under "Step 2 - Specify Components" not work? If not, does InstallShield or whatever you're using not have a similar option for installing the HTML Help engine along with the program?