G'day "Suzanne S. Barnhill" <sbarnhill@mvps.org>,
Ahhh! I see, a field that autosenses the last heading used and
auto-refers to it. Gee, that would be nice :-)
That sort of thing is what I use pre-production macros for. If it was
to be inline, I'd probably use tag text [LASTHEAD] and then come
publish time, make a copy & zap a macro through it to find these tags,
find the previous heading (reverse iterate paragraphs from tag to doc
start looking at outline levels) .and hard-insert the required
details.
Steve Hudson - Word Heretic
steve from wordheretic.com (Email replies require payment)
Without prejudice
Suzanne S. Barnhill reckoned:
What is usually desired is to sense the first heading (any level or any of
specified levels) on the page and replicate it. I personally feel this may
be poor design since the header would then reflect large chunks of content
in some cases and smaller chunks in others. I think it's probably better to
pick one level (usually the top level of subhead--which could be Heading 2
if Heading 1 has been used for the chapter title) and stick with it.

Signature
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Word MVP FAQ site: http://word.mvps.org
Email cannot be acknowledged; please post all follow-ups to the newsgroup so
all may benefit.
> G'day "Suzanne S. Barnhill" <sbarnhill@mvps.org>,
>
[quoted text clipped - 17 lines]
> >The problem is that there *will* be Heading 1 text in the *document*; the
> >trick is to limit the search to the page; and I don't think that's possible.
Word Heretic - 08 Jan 2005 02:06 GMT
G'day "Suzanne S. Barnhill" <sbarnhill@mvps.org>,
Yes, this would get very messy in most real world instances. It also
would never take the place of sensible structuring to start with.
Steve Hudson - Word Heretic
steve from wordheretic.com (Email replies require payment)
Without prejudice
Suzanne S. Barnhill reckoned:
>What is usually desired is to sense the first heading (any level or any of
>specified levels) on the page and replicate it. I personally feel this may
>be poor design since the header would then reflect large chunks of content
>in some cases and smaller chunks in others. I think it's probably better to
>pick one level (usually the top level of subhead--which could be Heading 2
>if Heading 1 has been used for the chapter title) and stick with it.
Marko Pinteric - 10 Jan 2005 08:31 GMT
I agree that this is a poor design. Unfortunatelly in specifications
for technical reports in civil engineering projects it HAS TO BE this
way. :-(
BTW, I *did* googled Internet for this specific problem and found no
solution.
Marko.
> What is usually desired is to sense the first heading (any level or any of
> specified levels) on the page and replicate it. I personally feel this may
> be poor design since the header would then reflect large chunks of content
> in some cases and smaller chunks in others. I think it's probably better to
> pick one level (usually the top level of subhead--which could be Heading 2
> if Heading 1 has been used for the chapter title) and stick with it.
Marko Pinteric - 10 Jan 2005 09:40 GMT
I *did* find this code today
{ IF {STYLEREF "Heading 2" \n }<{STYLEREF "Heading 1" \n } "{STYLEREF
"Heading 1" \n }" "{STYLEREF "Heading 2" \n }"}
but I don't know how to use it. That is, I insert code field, put the
text (I have to use "=" in the beginning, and Word reports synthax
error. I guess there is something wrong about how I put code fields
into Word.
Thanks for help,
Marko.
> What is usually desired is to sense the first heading (any level or any of
> specified levels) on the page and replicate it. I personally feel this may
> be poor design since the header would then reflect large chunks of content
> in some cases and smaller chunks in others. I think it's probably better to
> pick one level (usually the top level of subhead--which could be Heading 2
> if Heading 1 has been used for the chapter title) and stick with it.
Suzanne S. Barnhill - 10 Jan 2005 16:30 GMT
Every pair of field delimiters (those things that look like braces but can't
be typed from the keyboard) must be inserted using Ctrl+F9. As you can see,
there are several pairs nested within the outside pair, and you have to get
them right. Start by inserting one pair and typing IF, then insert
additional pairs for the StyleRef fields. Note that the TrueText and
FalseText do not need to be quoted since they are fields (only text needs to
be in quotes).

Signature
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Word MVP FAQ site: http://word.mvps.org
Email cannot be acknowledged; please post all follow-ups to the newsgroup so
all may benefit.
> I *did* find this code today
>
[quoted text clipped - 16 lines]
> > pick one level (usually the top level of subhead--which could be Heading 2
> > if Heading 1 has been used for the chapter title) and stick with it.