Peter, thanks for your input. Here's where we are. We opened
RoboHelp HTML and converted the Word docs into .html files. Then we
were able to generate the .chm file (it worked this time) using
RoboHelp HTML. We have about 50 .gif images, and no external links.
The actual number of HTML files with help topics is close to
4,000 for this F1 field help in our application. Ideally, we would
love to have a master project with sub-projects, but it doesn't
appear as a practical alternative. The .hh file (for F1 field help)
is generated from the application by the developer and given to us.
In order to have a master project and slave projects, we
would have to manually split that automatically-generated.hh file
into individual .hh files, true? That means we would have to
correlate which .html help topic file corresponds with which map id
number, then chalk out how we want to divide the .html help topics
into individual projects that correspond to their .hh files?
This help system I inherited is 10 years old, and the
resource time we would spend (if we chose to modularize this help
system) would be gigantic in scope. If there is a simpler and
efficient way to modularize our F1 help system, I would love to
hear about it!