Thanks Richard, that's what hapenned.

Unfortunatelly, there are numerous users and the file served based app was a good choice, now with the help support having to be installed/registered in each user's PC lead me to use a shellexecute() option for calling the .chm file, since it was not a context sensitive help, rather an online documentation.

Just for the record: I'm unsatisfied with the way VFP implements help support, making me use install routines.

Regards,

Fernando

>These need to be registered on the local machine with:
>
>Foxhhelp8.exe /regsrver
>regsvr32 foxhhelpps8.dll
>
>If they won't work from the server, you may need to copy them onto the local machine.
>
>Richard
>
>>Hi Richard, thanks for your reply!
>>
>>I copied Foxhhelp8.exe and Foxhhelpps8.dll to the file server, now do must I register those files in the file server?
>>
>>Fernando
>>
>>>You also need Foxhhelp8.exe and Foxhhelpps8.dll for vfp 8 and foxhhelp.exe and foxhhelpps.dll for vfp6 installed and registered.
>>>
>>>Richard
>>>
>>>>Hi,
>>>>
>>>>I'm trying to implement help support in a VFP app. For this purpose I put the necessary commands in my app and created a help (.chm) file.
>>>>
>>>>It all works fine when the app is run in my development machine. When I deliver the app to production (in a file server), and its users press F1 nothing happens.
>>>>
>>>>Any tips?
>>>>
>>>>In the file server the following files (VFP runtime version 8, SP1) are installed:
>>>>
>>>>gdiplus.dll
>>>>VFP6R.DLL
>>>>VFP6RENU.DLL
>>>>VFP6RUN.EXE
>>>>vfp8r.dll
>>>>VFP8RENU.DLL
>>>>vfp8t.dll
>>>>
>>>>TIA,
>>>>
>>>>Fernando