>>Ok, I have seen the reasons why our CHM help files no longer work on our client installations. I know that I can have the users copy the help file to their local drive and it will work when run from Windows Explorer. From an installation standpoint, this seems to be a little awkward. What is everyone else doing about their online help documentation if they are not copying the CHM files to local drives? Are there any other solutions where the help information can be stored on a network and called from a VFP application, possibly something other than CHM?
>
>You can still use the help.dbf format - the same as it was in 2.x - because it still works. Set help to yourhelp.dbf and there you go. Help displays in a VFP form which actually looks ugly, but then you can even write your own if you want. It has all the cross-links and other stuff, just no graphics.
>
>Alternately, if you're already doing your help files as chm, you've already made web pages to compile into chm. You can just have a subdirectory with all these web pages, and write some code to have them properly linked, with a treeview-like structure on the left etc. I've done that in FPD2.6 under Windows 98, and it displayed fine.

Hey Dragan

I'll pass on the dbf idea. I have some users who already use HTML Help Workshop and don't need another interface to learn/use.

I like the idea of using the html files. I guess it would be nice to somehow combine all of the .htm files that make up the chm file into one file and distribute it. It wouldn't be the end of the world if all of the .htm files had to be installed in a separate folder. Any chance you know of a 3rd party product that might combine them all into one file so it could be easily distributed?

Tim