Problem with field updates

[macropod]

Hi Jim,

The cause of the problem is fairly straightforward: The REF fields pick up
the last instance of the SET varMonth field which, of course, is December.

For each section, try something like:
{QUOTE "1/{SEQ varMth}/0" \@ "MMMM"}
or
{QUOTE "1/{SECTION}/0" \@ "MMM"}

Cheers

 

[Jim]

I have a very strange problem with a long (429 page) document. The document
is broken into Monthly sections, and at the beginning of each month I have
the following field code (with the obvious name of the month changes).

==================
{SET varMonth "January" }
{REF varMonth}
{SEQ varDay \r 1}
==================

Then for all other days in the month I simply have:

==================
{REF varMonth}
{SEQ varDay \c}
==================

This easily sets headlines within the document and document header values.
The problem I have is that when I'm in normal view the fields update
appropriately. But whenever I go to Print View or Print Preview the fields
recalculate and all the Month field REFs change to December. If I go back to
Normal View, Select All, and Update Fields they all update appropriately.

Things I've tried so far:
I looked through the document several times for a rogue SET field but have
not found one.
I have tried several Tools, Options setting such as Print, Update Fields but
nothing seems to change the behavior.


Any help would be greatly appriciated. I am using Word 2002 SP3.

 

[macropod]

Hi Jim,

I suspect the problem is more to do with how things are displayed in
'Normal' view than how things are displayed in 'Page Layout' view. The
fields may not be updating correctly in 'Normal' view.

In either view, if you were to print the document you should get the same
result as you see in 'Page Layout' view.

Cheers

 

[Doug Robbins - Word MVP]

I would suggest that you post your question to the
microsoft.public.word.mailmerge.fields newsgroup. There's a guy named
macropod who frequents that group who is I believed the acknowledged guru as
far as fields are concerned.

--
Please post any further questions or followup to the newsgroups for the
benefit of others who may be interested. Unsolicited questions forwarded
directly to me will only be answered on a paid consulting basis.

Hope this helps
Doug Robbins - Word MVP

 

[Jim]

Macropod,

Thanks for the suggestion...But it really is strange behavior that a manual
update will provide the solution I'm looking for but the field update that is
done as part of the print/print preview process doesn't.

Again, thanks for the tip.