View Single Post
  #5   Report Post  
Posted to microsoft.public.word.pagelayout
Suzanne S. Barnhill Suzanne S. Barnhill is offline
external usenet poster
 
Posts: 33,624
Default "Same as previous" loses an item midway thru doc

I didn't say it was pointing to the wrong style. I said that you very likely
have that style applied to something that's blank. Use Find to search for
the style in the vicinity of that StyleRef and see if Find stops on some
place that is NOT a heading (or whatever else it is that you're using the
StyleRef to pick up).

It's always a good idea to omit section breaks if they aren't needed; adding
them just makes the document unnecessarily complex. Instead of using the
browse arrows (or Ctrl+PageDown/PageUp) to go to the next or previous
section, would it work to go to the next or previous heading? Set Heading as
the browse object and you can use the same shortcuts.

--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
http://word.mvps.org

"christophercbrewster via OfficeKB.com" u3143@uwe wrote in message
news:a35712ab24572@uwe...
Suzanne S. Barnhill wrote:
Are you sure the field itself is really missing?


I thought I knew the answer to this, but you're right: F9 does show the
field.
It's not there if you just try pointing to it, however.

If the field is still there but is not resulting in any text, then it is
almost certain that the style has been inadvertently applied to a blank
line, page break, or the like.


No, it's pointing to the correct style, and it displays correctly in
earlier
sections before something changes it. I tried copying and pasting the same
field from a header where it works correctly, and it briefly shows and
then
disappears.

... I would guess that the section breaks are necessary for some other
reason, such as chapter openings with a different First Page Header?


Actually the best use for them is to use Go To next or previous section,
which are assigned to keys. But the footer and header definitions don't
change. Maybe that isn't a good enough reason to deal with this problem?

--
Christopher Brewster
Lockheed Martin, Eagan MN

Message posted via http://www.officekb.com