For example: the document is up to an even page. Then
comes a table on a single landscape page, followed by
another protrait page. But the portrait page has the
wrong margins (those for an odd page rather than an even
page). If I go back & change the section break before the
table (which was inserted as a plain section break but is
now claiming to be an Even page break) to an Odd page
break, the margins on the portrait page are fixed but now
the page numbers skip a page (the table is on page 9,
whereas it should be page 8). Trying to use brute force &
change the 'starting page' number in the footer doesn't
work: it refuses to consider that page to be #8. Every
time I find a way to fix one problem (margins or page
numbers), the other one gets broke. Aargh!
Any help appreciated.
--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Word MVP FAQ site: http://www.mvps.org/word
"Sara Cairns" <sca...@dred.state.nh.us> wrote in message
news:211801c1c9eb$8e611870$35ef2ecf@TKMSFTNGXA11...
After a lot of trial & error, my current workaround is to
delete every Odd or Even section break that shows up &
replace it with a plain vanilla one, then re-apply all the
Landscape page setups (and Footers).
>.
>
I have run into a very similiar problem with items in the
header that had to be on the "outside" when the document
was bound. The thing that finally helped me understand
what was going on was to realize that when the
header/footer says "same as previous" it means "same as
the previous" odd or previous even page - whichever you
are on. It's as if the odds in a section are one section
and the evens are another section, based on the way it
acts. (I also kept running into the setting that made the
first page of a section different, or the page numbering
was starting on "7" or some other random number. I really
thought I had gone insane!) I think I ended up checking
all the settings starting at the end of the document and
moving backwards through the settings for the odd page in
each section then the even in that section.
I don't think this solves your problem but maybe it will
give you something to build on.
>.
>