No worries re the posting - we don't do top/bottom/in-line flamewars in here
;-)
Word holds the values for the first page H&F whether you have different
first page on or off - that's why you get your header back when you switch
manually. So there shouldn't be an order of work problem - just make sure
you set the first page footer at the same time as the primary one.
If you need to cater for multi-section documents, overriding footers that
are not Same As Previous, you can do that by iterating through the Sections
collection. But since Same as Previous is the default, that situation can
only arisen if someone has gone into H&F view and explicitly turned it off.
In the unlikely event that they actually knew what they were doing, perhaps
setting a footer for a landscape page or removing a footer on page with a
large table or figure, you might not be too popular. A warning message about
multiple sections might be nicer?
--
Margaret Aldis - Microsoft Word MVP
Syntagma partnership site:
http://www.syntagma.co.uk
Word MVP FAQ site:
http://www.word.mvps.org
"grlgeek" wrote in message
...
Sorry, I didn't realize the standard in this group was for top-posting.
I'll top post and I've trimmed my previous info so its a bit clearer.
Thank you for your suggestions and I'm going to try some of your stuff.
I have access to the global template modules to make edits, so I am going
to try your section suggestions.
I can't use fields in the footer for a couple reasons. 1. we use a
document management software for file storage that stores username, date
and filename in a sql database format. and 2. I could implement the new
footer w/ form fields on the normal.dot for all new documents and go thru
thousands of templates to add to them - (but wouldn't be able to update
them properly at that point) but we also have hundreds of thousand
documents in the system that would possibly be affected by this kind of
change - a daunting task to say the least.
So I just need to work the logic out here.
1. Turn off different first page, but also get the save to copy footer to
page 2
2. allow for section breaks that use "same as previous" (but this has
been
known to lead to bugs and corrupted documents in the past, so its best to
avoid).
Oh hell with it - if Admin Assistants actually knew how to use Word we
wouldn't have this problem in the first place, but the job pool in that
area is so limited these days its pathetic. Its a sad day when the
network administrator is the most knowledgable at Word, Excel, PPT and
other office related software in the company.
On Thu, 19 May 2005 19:26:41 +0100, Margaret Aldis wrote:
Bottom posted to keep OP's flow.
Surely the simple solution is to:
a) change your template so that the footer information (both first footer
and following page footer) is set up using fields. All these items are
routinely included in documents in this way - use SAVEDATE for the date
the
document was last saved, or CREATEDATE if you want the date it was
created.
b) change the global template so it doesn't mess with the page layout,
but
does update fields. The easiest way of updating the footer is to do a
view
swap into Print Preview and back.
If there is some reason why the macro really does need to directly write
to
the footer, then write it to the first page footer as well as the normal
footer and leave the page layout alone. That is, write the same text to
ActiveDocument.Sections(1).Footers(wdHeaderFooterF irstPage).Range.Text
as you write to
ActiveDocument.Sections(1).Footers(wdHeaderFooterP rimary).Range.Text
If you can't get at the global macro but need a way of ameliorating the
situation at the coal face, then see if you can match the footer
information
with fields in the first page footer (that will spring back into life
when
you switch the first page layout on again). |Or as a last resort you
could
write a macro that will turn the first page back on, pick up the ordinary
footer and insert it in first page footer. Note that you'll need to
remove
the extra paragraph break you get if you just set
ActiveDocument.Sections(1).Footers(wdHeaderFooterF irstPage).Range.Text =
_
ActiveDocument.Sections(1).Footers(wdHeaderFooterP rimary).Range.Text