>You should definitely get away from the VFP database-style help! If your Word Processor is Word, there are several doc-to-help packages out there - but if you're using a different word processor, I'd suggest looking at ForeHelp.
>
>We're also on the cusp of a change from the common 'Windows-Style' help format to an HTML format - you should probably go directly to HTML help files! I think the current version of ForeHelp handles both.
>
>Some may say that usiing Word as a basis for your help files allow you to write your documentation once. I don't buy it! The proper format and organization for a help file is different enough to require massaging (althoug you'll do a lot of cut-and-paste as well).
>
>FWIW
>
>>Unless it's simply my imagination, creating help in VFP is a bit of a pain. Anyone have any suggestions for developing a context-sensitive help system which can be used through VFP?
>>
>>TIA!
>>
>>Mark W. Mitchell
>>mark@remarkable-systems.com

Michael,

Thank you for the insite. It turns out that per your advice (and several others), I have chosen ForeHelp; the Premier Suite includes HTML help capabilities.

I have understood this trend to be true, but my question is this...
if I do HTML help over WinHelp, my users are then required to have some sort of browser. I realize this is quite common, but not definite. And is there a problem based on which browser a person uses? Netscape... IE? Does it matter?

Also, won't the HTML help appear exactly as if the users went to my website and starting clicking on links? If so, then wouldn't it be better to simply put the help online so it's always up-to-date? Granted, users would be required to have access to and attain access to the Internet before Help would become available. And finally, if HTML help appears / acts the same on the Internet as it does locally, then why something like ForeHelp? Why can't someone just use their HTML editor, such as FrontPage?

Thanks!

Mark