Errors on creating new Topic in RH9 (9.02 Patch)

Question

Have found that when creating a new topic in RH9 project that on building the project errors 3018 and 3111 are being presented.
Appears that the error is being caused by the placement of the Page Break in the word document at the commencement of the topic.  Prior versions of RH would insert a new topic as such :-  (Note correct placement of Page Break and 'Keep with next' paragraph mark).
When adding a new topic now it appears as such :-
Note the placement of the 'Keep with next' paragrah mark is now at the start of the topic line rather than at the start of the page break.
On building then project with a topic in this format causes 2 additional error messages to be presented in error wizard :-
1.  HC3018: Warning: In the project file, an #include statement is specified without a filename,  and
2.  HC3111: Warning: This topic contains keywords but no title
The second warning (HC3111) is returned despite the topic properties containing a title, and keyword sections correctly filled out.
I have found that the work around to fix this is to correct error HC3018 first by :-
Place Cursor at start of the topic line immediately prior to the # symbol.
Back space to remove the 'Keep with next' paragra[ph mark to a point where the mark is removed, the heading properties are removed from the topic title and the Page break indication now extends across the entire page.
With Cursor placed at the commencement of the topic line again immediately prior to the # symbol, re-apply the 'Keep with next' paragrah command.  This applies the command on the 'Page break' line.
Re-apply Heading style to the topic line.  It now looks line this :-
Re-build project. Error messages 3018 and 3111 now both gone.
Yet another bug in this version now doubt.

Answer 1

Peter G,
Thanks.  Tried that and no the problem does not present in a new project.  Oddly enough this started occurring in a new project that had these documents imported from  a previous project (word 2003 format into Word 2010 format).
So it doesn't occur by default in a new project, but does in an older project migrated from 2003 word format into 2010 format.  Go figure.
David H.
Thanks to you for your suggestion.  Worked fine.  Not sure why all of a sudden I have to do this and why the same issue does not occur in new project by default,  Maybe a word 2003 to word 2010 save / convert issue ?
Nonetheless your suggestion and fix works well and far less painful than my clumsy solution.
Once again,  Thanks to both of you for your assistance