I have been experiencing the same problem when using RoboHelp HTML 7 to import an MS Word .doc file and create WebHelp output. I am using MS Word 2007 but keeping the file as a .doc file - MS Word 97-2003 compatible. This import and WebHelp creation process worked fine before - during more than one conversion RoboHelp HTML 7 created one HTML file per Heading 1 style - with the same MS Word input file but this time around the import created a single HTML output file containing all Heading 1 styles rather than treating each as an endpoint for an HTML file.

I deleted unused styles from the MS Word source file and confirmed that in fact "real" Heading 1 styles were used. I even created a simple dummy file with the default Heading 1 and Heading 2 styles from MS Word's normal.dot and still experienced the same problem. This convinced me that it is a RoboHelp HTML 7 code bug.

The workaround I discovered consists of placing a section break continuous - possibly bracketed by Normal style paragraph marks if this proves convenient (the previous section ends with a table) or necessary (RoboHelp HTML still ignores the Heading 1 style as a file endpoint) - immediately before the Heading 1 style that is not treated properly by RoboHelp HTML 7. This approach changes the page layout slightly but that is a small price to pay.

One side effect of this workaround seems to be that the table of contents (TOC) in RoboHelp HTML isn't quite right after import and prior to WebHelp files creation. This TOC anomaly occurred at the first Heading 1 that was formerly ignored by RoboHelp HTML 7 as a file endpoint (this is the second Heading 1 in the MS Word file). The anomaly shows up as a TOC heading that points to the HTML file associated with the prior Heading 1 paragraph. For example if the source MS Word file contains Heading 1 paragraphs named "Heading 1 First Instance", "Heading 1 Second Instance" and "Heading 1 Third Instance", then after import the TOC entry for "Heading 1 Second Instance" points to the HTML file associated with "Heading 1 First Instance". This anomaly is easily correctable by adding a new TOC entry for the HTML file associated with "Heading 1 Second Instance". The bottom line is that you'll need to check each TOC entry after import and make sure that each one points to the correct HTML file.

When you import with RoboHelp 7 a dialog displays showing all the styles RoboHelp recognises as headings. Are the style being displayed in that dialog and are they ticked?

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge