Outline won't promote/demote

[Laura]

When I create my own styles and then link them to an
outline, the promote/demote feature (Shift+alt+arrow)
doesn't work. I have set the "outline level" in style for
each paragraph. Created the styles first, linked the first
one to an outline and then, from w/in the outline clicked
through the levels linking to the other styles, but it
won't work. I even tried basing the level2 style on
level1, level3 on level2, etc., Nada!

I did this on another computer and it worked, but on
seeral other computers it won't work.

I don't want to use the built in heading styles because
sometimes I need more than one outline in a document, and
there is only one set of heading styles.

Any ideas would be GREATLY appreciated.

Many thanks.
Laura

[Suzanne S. Barnhill]

I have a vague idea that this works only with Word's built-in outline
styles: the heading series and the various list series. You might try using
List Number and List Bullet instead of your custom styles (they don't have
to be numbered or bulleted).

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

"Laura" <LTow...@stsTrain.com> wrote in message
news:32ee01c1edbf$9cf93a00$3aef2ecf@TKMSFTNGXA09...

[Dave Rado]

Hi Suzanne

It works with any properly defined outline numbering scheme, regardless of
styles.

What's confusing you is that it also works with *unnumbered* Heading styles
but only if they're the built-in ones.

Regards

Dave

"Suzanne S. Barnhill" <sbar...@mvps.org> wrote in message
news:#vlzc8e7BHA.972@tkmsftngp05...

[Dave Rado]

Whoops - correction - it works with all properly set up numbering styles
(built-in or otherwise) *except* in the case of headings - for headings it
only works with the built-in styles.

Regards

Dave
.

"Dave Rado" <dr...@onetel.net.uk> wrote in message
news:#YaPO5h7BHA.1212@tkmsftngp02...

[Dave Rado]

Hi Laura

If you mean that you want ordinary Heading numbering for the main headings,
and appendix numbering for the appendices, there are two ways of catering
for this.

1) If you don't want to write complex macros, use Heading 1 - Heading 5 for
you main Headings, and Heading 6 - Heading 9 for your appendix styles - link
them all to *one* outline definition. In your TOC definitions (under
Options), you can stipulate that you want Heading 6 to appear at level 1 in
the TOC, heading 7 at Level 2, etc.. This is the method most people use,
because it requires no programming. It works very well, although it has
(what I consider to be) the major disadvantage that when you go into Outline
View, your appendices are hidden away at levels 6-9.

2) Alternatively - and this is what I do - use separate style sets and
outlines as you are doing for your main headings and your appendix headings
(although I *would definitely* use the built-in styles for your main
headings); and intercept the OutlinePromote and OutlineDemote commands with
macros that promote and demote non-built-in heading styles as well as
built-in ones. What makes the macro complex is catering for the scenario
where the user has selected a whole bunch of headings and their subheadings
and wants to promote or demote them in one go (which is how Outline View
ought to be used).

Regards

Dave

"Laura" <LTow...@stsTrain.com> wrote in message
news:32ee01c1edbf$9cf93a00$3aef2ecf@TKMSFTNGXA09...

[Laura]

Dave and Suzanne --

First, thank you BOTH! I've been learning tons from both
of you over the past couple weeks...

Dave you said:
"and intercept the OutlinePromote and OutlineDemote
commands with macros that promote and demote non-built-in
heading styles as well as built-in ones."

Any idea where I can get a clue on this code?

I've tried the outline promote code (Just recorded myself
promoting/demoting heading styles) but it doesn't work for
my homemade styles.

Ultimately, I actually am writing a macro to do this. So
far I've been able to have it search for existing style
names and create them if they don't exist, search for an
existing list template and create it if it doesn't exist.
Then link the style names (level 1 through 9) to the new
list template. I also tried this manually by just
creating styles and then linking them to an existing word
list galleries template. BUT THE DAMNED THING WON'T
PROMOTE. I see macro packages that do this w/ outlines
linked to non-built in styles all the time. Madness!!!!!

Again, thanks for all your help. If my head doesn't
explode first this will be real cool when I'm done with
it!!!!!

>.
>

[Dave Rado]

Hi Laura

As I said, the Promote/Demote code is very complex to write; why not use the
other technique, which doesn't require macros?

BTW, if the style doesn't exist, why not simply update the styles from the
template? (Taking on board the qualifications described at:
http://www.mvps.org/word/FAQs/MacrosVBA/UpdateStyles.htm).

Regards

Dave

"Laura" <LTow...@stsTrain.com> wrote in message

news:324b01c1ee2c$81c94eb0$39ef2ecf@TKMSFTNGXA08...

[Laura]

Thanks Suzanne. I haven't played with the "list styles"
at all. Maybe I could have outline #1 (the main one for
the document) use the heading styles, and then Outline #2,
when it's needed use the list styles.

I just don't see why it won't promote/demote if it's
properly linked to an OUTLINE LIST TEMPLATE!!! Do I ask
that much!!!!????

Thanks for the ideas. Back to the ole salt mines...

>.
>

[Laura]

Hi,

My resistance to using the built in heading styles is that
this is for legal documents and the users (occasionally)
need all 9 levels of an outline for one area of the
document (a legal brief) and then elsewhere (in their
exhibits, I think) need a totally different outline. So
utilizing just parts of one outline for what will "appear"
to be different outlines in one document may not give
enough levels.

But I do want to keep this SOMEWHAT simple. Although it
may turn out that my resistance is futile! If I do what
Suzanne suggested and use the heading styles for one list
and the list styles for another, both of which will
promote/demote based on Shift+alt+arrow, that would work.

As for the style coming from the template -- my original
thought was to have one numbering utility for all
documents and let the user give a "name" to their outline -
- then build the outline using styles based on that name
(like PleadingL1, PleadingL2, PleadingL3, etc.) Now I
could just teach them that "Heading1 is level 1, Heading2
is level2, etc, but then when they need multiple outlines
in one document, I'm, er, screwed...

I'm going to check out the MVP link you gave me. I've
actually come a long way reading through some of the
numbering threads in which you posted (Nightmare on
numbering street) etc. But my knowledge is still WAY FULL
of holes!

Thanks for all your help.

>| >"LaÍ{ wÀ 4ÙÐ Ü#N ü, ìÀ ura"

[Klaus Linke]

Hi Laura,

I just wrote macros to replace the built-in commands for
OutlineDemote/OutlinePromote.

They were aimed at making them work in tables (where they don't work
in Outline view). But they should also work fine for custom headings.

Just put them in your template; since they have the same names as the
built-in commands, they are automatically called if you hit the
promote/demote buttons or use Alt+Shift+Left/Right.

Regards, Klaus

Sub OutlineDemote()
Dim myPara As Paragraph
Dim myOL
For Each myPara In Selection.Paragraphs
myOL = myPara.Style.ParagraphFormat.OutlineLevel
Select Case myOL
Case wdOutlineLevel1
myPara.Style = wdStyleHeading2
Case wdOutlineLevel2
myPara.Style = wdStyleHeading3
Case wdOutlineLevel3
myPara.Style = wdStyleHeading4
Case wdOutlineLevel4
myPara.Style = wdStyleHeading5
Case wdOutlineLevel5
myPara.Style = wdStyleHeading6
Case wdOutlineLevel6
myPara.Style = wdStyleHeading7
Case wdOutlineLevel7
myPara.Style = wdStyleHeading8
Case wdOutlineLevel8
myPara.Style = wdStyleHeading9
Case wdOutlineLevel9
myPara.Style = wdStyleBodyText
Case wdOutlineLevelBodyText
myPara.OutlineDemote
End Select
Next myPara
End Sub

Sub OutlinePromote()
Dim myPara As Paragraph
Dim myOL
For Each myPara In Selection.Paragraphs
myOL = myPara.Style.ParagraphFormat.OutlineLevel
Select Case myOL
Case wdOutlineLevelBodyText
If myPara.Style.ListTemplate Is Nothing Then
myPara.Style = wdStyleHeading1
Else
myPara.OutlinePromote
End If
Case wdOutlineLevel9
myPara.Style = wdStyleHeading8
Case wdOutlineLevel8
myPara.Style = wdStyleHeading7
Case wdOutlineLevel7
myPara.Style = wdStyleHeading6
Case wdOutlineLevel6
myPara.Style = wdStyleHeading5
Case wdOutlineLevel5
myPara.Style = wdStyleHeading4
Case wdOutlineLevel4
myPara.Style = wdStyleHeading3
Case wdOutlineLevel3
myPara.Style = wdStyleHeading2
Case wdOutlineLevel2
myPara.Style = wdStyleHeading1
Case wdOutlineLevel1
End Select
Next myPara
End Sub

[Dave Rado]

There's no reason except that the designers at Microsoft weren't thinking
straight. I hope you'll email msw...@microsoft.com.

Regards

Dave

"Laura" <LTow...@stsTrain.com> wrote in message

news:2e9d01c1ee40$eefdc290$9ae62ecf@tkmsftngxa02...

[Dave Rado]

Hi Klaus

If I go into Outline View, select "Show Heading 1", click on a Heading 1
paragraph and press Alt+Shift+Right, the subheadings under it don't get
demoted, but some of the body text paragraphs do..

Also, if I click on a List Number paragraph and click demote, instead of
being demoted to List Number 2, it gets converted to a Heading.

Regards

Dave

PS - MS don't really support the use of Heading styles in tables - they
don't show up in Outline View. IMO, it's best to avoid using them if
possible (i.e. split the table and put the headings in the paragraph between
the tables).

"Klaus Linke" <fotosatz...@t-online.de> wrote in message
news:aafokp$dgd$02$1...@news.t-online.com...

[Dave Rado]

Hi again Klaus

Sorry, I should have made it clear that I don't get that behaviour unless I
use your macro - using the built-in commands, in the first example, all
subheadings of the heading I demoted get demoted and no body text does; in
the second example, the List Number paragraph gets demoted to List Number 2.

Regards

Dave

"Dave Rado" <dr...@onetel.net.uk> wrote in message

news:#M$le1p7BHA.972@tkmsftngp05...

[Klaus Linke]

I think I should tie my right index finger behind my back when
visiting the newsgroups -- I hit the send button too easily ;-)

The macros I posted are buggy in several ways, and don't work at all
with custom headings.

The error Dave discovered is caused by a bug in Word2000: If you don't
display all levels in Outline View, VBA will report the wrong style
for the paragraph the cursor is in; try
MsgBox Selection.Paragraphs(1).Style.NameLocal

As far as I can see, this is caused by another bug: If you don't
display all levels and count the paragraphs in some Range or
Selection, only those paragraphs that are displayed are counted. But
internally, Word still numbers all paragraphs. So if you try to get
some information for the third displayed paragraph, Word will return
the information for the paragraph with .Index = 3.

And while we are at it: If you select a paragraph while only "Level 1"
levels are displayed, the style dropdown doesn't display anything. And
for any paragraph, you can not get the outline level while you are in
Outline View -- bummer!

I'll try to find a way around these bugs. But for the time being,
below are macros that hopefully work fine as long as you display all
levels in Outline view. They should work with custom headings, as long
as they are numbered from 1 to 9 ("My Heading 1", "My Sub-Heading 2"
..., "Appendix Heading 9").
Paragraphs without outline level and list level will be promoted to
"Heading 1".

Greetings, Klaus

Sub OutlineDemote()
Dim myPara As Paragraph
Dim myOL

Dim myStyleName As String
Dim myLevel As String

For Each myPara In Selection.Paragraphs
myOL = myPara.Style.ParagraphFormat.OutlineLevel

myStyleName = myPara.Style.NameLocal
Select Case myOL
Case wdOutlineLevel1 To wdOutlineLevel8
myLevel = ""
While InStr(1, "0123456789", _
Right$(myStyleName, 1)) > 0
myLevel = Right$(myStyleName, 1) & myLevel
myStyleName = Left$(myStyleName, _
Len(myStyleName) - 1)
Wend
myLevel = Trim(Str(Val(myLevel) + 1))
myStyleName = myStyleName & myLevel
myPara.Style = myStyleName

Case wdOutlineLevel9
myPara.Style = wdStyleBodyText
Case wdOutlineLevelBodyText

If myPara.Style.ListTemplate Is Nothing Then

' do nothing
Else
myPara.OutlineDemote
End If

End Select
Next myPara
End Sub

Sub OutlinePromote()
Dim myPara As Paragraph
Dim myOL

Dim myStyleName As String
Dim myLevel As String

For Each myPara In Selection.Paragraphs
myOL = myPara.Style.ParagraphFormat.OutlineLevel

myStyleName = myPara.Style.NameLocal

Select Case myOL
Case wdOutlineLevelBodyText
If myPara.Style.ListTemplate Is Nothing Then
myPara.Style = wdStyleHeading1
Else
myPara.OutlinePromote
End If

Case wdOutlineLevel2 To wdOutlineLevel9
myLevel = ""
While InStr(1, "0123456789", _
Right$(myStyleName, 1)) > 0
myLevel = Right$(myStyleName, 1) & myLevel
myStyleName = Left$(myStyleName, _
Len(myStyleName) - 1)
Wend
myLevel = Trim(Str(Val(myLevel) - 1))
myStyleName = myStyleName & myLevel
myPara.Style = myStyleName

Case wdOutlineLevel1
End Select
Next myPara
End Sub

[Klaus Linke]

S..s..s...Sorry for p...p...posting this as a serialized novel, but it
took me a while to fix everything (hopefully).

The bugs and limitations in Outline View are too bad to make
OutlinePromote and OutlineDemote work properly in this view.

Therefore I have resorted, as a workaround, to switch to Normal view
temporarily:

Dim myViewType
myViewType = ActiveWindow.View.Type
Application.ScreenUpdating = False
ActiveWindow.View.Type = wdNormalView
' ... old code ...
ActiveWindow.View.Type = myViewType
Application.ScreenUpdating = True

Below are the new macros.

Regards, Klaus

Sub OutlineDemote()
' works with custom headings that end with consecutive numbers
' (for example "Appendix H1" to "Appendix H9")
' Fixes bugs working with tables in OutlineView

Dim myPara As Paragraph
Dim myOL
Dim myStyleName As String
Dim myLevel As String

Dim myViewType
Application.ScreenUpdating = False
myViewType = ActiveWindow.View.Type
ActiveWindow.View.Type = wdNormalView

ActiveWindow.View.Type = myViewType
Application.ScreenUpdating = True
End Sub

Sub OutlinePromote()
' works with custom headings that end with consecutive numbers
' (for example "Appendix H1" to "Appendix H9")
' Body text is promoted to "Heading 1"
' Fixes bugs working with tables in OutlineView

Dim myPara As Paragraph
Dim myOL
Dim myStyleName As String
Dim myLevel As String

Dim myViewType
Application.ScreenUpdating = False
myViewType = ActiveWindow.View.Type
ActiveWindow.View.Type = wdNormalView

For Each myPara In Selection.Paragraphs
myOL = myPara.Style.ParagraphFormat.OutlineLevel
myStyleName = myPara.Style.NameLocal
Select Case myOL
Case wdOutlineLevelBodyText
If myPara.Style.ListTemplate Is Nothing Then
myPara.Style = wdStyleHeading1
Else
myPara.OutlinePromote
End If
Case wdOutlineLevel2 To wdOutlineLevel9
myLevel = ""
While InStr(1, "0123456789", _
Right$(myStyleName, 1)) > 0
myLevel = Right$(myStyleName, 1) & myLevel
myStyleName = Left$(myStyleName, _
Len(myStyleName) - 1)
Wend
myLevel = Trim(Str(Val(myLevel) - 1))
myStyleName = myStyleName & myLevel
myPara.Style = myStyleName
Case wdOutlineLevel1
End Select
Next myPara

ActiveWindow.View.Type = myViewType
Application.ScreenUpdating = True
End Sub

[Laura]

Bless your heart. Where do I sent the check????

I was starting to head down this road -- changing the
style. I was doing a bunch of "if it's the level 1 style,
then make it the level 2 style" type stuff. I think the
case statements will be faster and you're looking for the
outline level rather than a style name, which I hadn't
though of! -- I need to read up on the case command, it's
always sort of confused me...

By the way -- I found this type of thing doesn't work in
outline view even if it's not in a table -- but I can
always check for outline view and switch them to something
else. I don't think the users typically work in outline
view.

I'm curious ... when your code says:
myPara.Style = wdStyleHeading# --
that doesn't apply one of the built in heading styles?

Thanks a lot. I'm going to go play with this.

>.
>

[Laura]

You guys are a huge help.

This is word 2002, so hopefully it will be less "buggy"...
I don't see any reason why I can't capture the current
view and switch them to normal or print layout prior to
executing -- do you? Maybe even switch them back to the
original view afterwards.

Although this may make the macro kind of "time consuming"
for just changing a level! Something they may do a lot.

>...., "Appendix Heading 9").

> myPara.OutlinePromÍ{ wÀ ¤ÌiHüâNH,, ì ote

[Laura]

>-----Original Message-----
>S..s..s...Sorry for p...p...posting this as a serialized
novel, but it >took me a while to fix everything
(hopefully).

Klaus:

Let me make sure I understand... You're spending your
time helping me fix my big dilemna. A dilemna, mind you,
that results largely from the fact that I don't know what
the heck I'm doing and don't have time to read several VBA
books and/or take classes (Translate to -- I don't have
time and want someone else (who has taken the time) to
just give me the answer...) AND THEN you're even testing
the code for me.

AND NOW you are APOLOGIZING for so many posts...

The world needs more people like you!!!!!!! Seriously,
where do I send the check?

[Laura]

Thanks, I will, and that email address is going in my
contacts right now...

You know, I'm a software trainer for law firms and MANY of
my clients are ex-WordPerfect people being drug KICKING
AND SCREAMING to Word by their clients who want to
exchange documents.

I tell my students -- Word is a THING OF BEAUTY once you
understand it. It was just DESIGNED WELL. Like there was
forethought, and you can control it once it's customized.

And then I see something like this and wonder...Why????
what were they thinking? That no one would ever use more
than one outline in a doc? That it's a reasonable
expectation they should pay a programmer to make it work
the way it's intended to work in the first place? It
seems so short sighted compared to the way most things
work in Word. And good, indepth info on numbering seems
so hard to scrounge up. (I've looked in a few VBA books
and the topic seems to be skipped.)

But I digress way past the purpose of this forum. Again,
thanks so much for all your help. I'm light years beyond
where I was...

Laura

>.
>

[Klaus Linke]

> I'm curious ... when your code says:
> myPara.Style = wdStyleHeading# --
> that doesn't apply one of the built in heading styles?

It did apply the built-in heading styles <blush> ...
That was the main reason for the profuse apologies in my previous
reply. I hardly checked the macros at all before posting them
yesterday.

If you find that some of the bugs have been fixed in Word2002, that
would be good news. Most of what I heard up to now indicated that few
old bugs have been fixed, and new ones appear on the scene.

> Seriously, where do I send the check?

Since there is no dedicated charity organization for Word victims,
http://www.un.org/ha/ (or choose any of your liking).

Greetings, Klaus

[Dave Rado]

Hi Laura

| I tell my students -- Word is a THING OF BEAUTY once you
| understand it. It was just DESIGNED WELL. Like there was
| forethought, and you can control it once it's customized.

As long as you don't use the List Numbering feature. :-)

Regards

Dave

[Dave Rado]

Also re:

| And then I see something like this and wonder...Why????
| what were they thinking? That no one would ever use more
| than one outline in a doc?

You can use as many outlines as you like, and all outlines that are linked
to styles that have an outline level of body text will promote and demote
fine. IOW, list numbering and list bulleting styles will promote/demote
fine.

It's just that outlines linked to *Heading styles* that aren't built in
don't promote/demote.

Regards

Dave

[Dave Rado]

Hi Laura

| I don't think the users typically work in outline
| view.

Not when editing text; but when promoting/demoting, it can save them *loads*
of time if they are trained to use OL view properly - see:
http://www.mvps.org/word/FAQs/Formatting/UsingOLView.htm

Regards

Dave

[Laura]

Dave,

Actually -- I'm a big proponent of Outline view and I find
that my attorney clients love it 'cause they can rearrange
a document easily, so maybe when I'm through with them
they WILL be working in Outine view more!

I'm going to read that article to make sure I'm not
missing any of the finer details. THANKS THANKS THANKS.

>.
>

[Suzanne S. Barnhill]

Now I'm confused. Either you left out a "not" or this is completely
backward. How can you have outline levels that are body text and
promote/demote them? Aren't outline style automatically Level 1, Level 2,
etc., and *not* body text?

Also, here's a poser for you. Since there are only nine outline levels, and
they're all visible in the list in the Customize Outline Numbered List
dialog, why is there a (grayed-out) scroll bar?

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

"Dave Rado" <dr...@onetel.net.uk> wrote in message
news:ulR9A0u7BHA.1696@tkmsftngp05...

[Laura]

Hi Suzanne,

I'm not Dave, but I "think" I can answer. When you define
a style, in the paragraph formatting you can set the
outline level. That's ONE thing.

If you define a few styles like, say, "lev1, lev2, lev3,
etc." you can then link them to AN OUTLINE (List template
from the list gallery). That's ANOTHER thing.

SO, ostensibly, you could set up a bunch of styles w/
paragraph levels of "body text" and then LINK them to "an
outline" (read: list template).

REGARDLESS, my experience is that unless the styles ARE
heading1 through 9 (which already have the outline levels
set) OR "based on" heading1 - 9 (in which case you have to
deal w/ them changing if anyone modifies a feature for a
heading style in the document that isn't contradictally
defined in the "based on" style) THEY SIMPLY WILL NOT
PROMOTE/DEMOTE properly.

(I think thepromote/demote feature may ACTUALLY change the
outline level for the paragraphs, but it WON'T jump you to
the style linked to the NEXT level of the outline.

BTW: Many people think the TOC, Document Map, and Outline
View rely on the fact that the styles used are the built
in "Heading styles" but if you create your own styles and
w/in them define outline levels other than body text,
these features will work with them. (but again, while the
outline view will show them for the outline they are, it
won't swap the styles for you when they're linked to a
list template)

>.
>

[Dave Rado]

If your custom styles are linked to a List Template (i.e. a numbering
definition), and if they have an outline level of body text, they *will*
promote and demote fine. It's only when you define them as having an
"outline level" (which should really be called heading level - outline
levels have *nothing* to do with numbering) that they won't promote or
demote.

If the custom Heading styles with an outline level were *not* linked to a
properly defined List Template this behaviour would make sense - how would
Word know what style to promote/demote the current style to? But if the
styles are linked to a properly defined List Template then there is no
logical reason why promote/demote shouldn't work, but it doesn't - it's just
very bad design by MS.

IME basing custom Heading styles on Heading 1-9 makes no difference to this
at all. If the styles are not built-in, and if they have an outline level
they will not promote/demote. End of story.

Regards

Dave

"Laura" <LTow...@stsTrain.com> wrote in message

news:7b7101c1ef3d$fa19e890$b1e62ecf@tkmsftngxa04...

[Suzanne S. Barnhill]

Thanks, Dave and Laura. I'm beginning to get the picture. I was
thoughtlessly assuming that the outline (list) levels in Format | Numbering
were always identical to the outline (heading/TOC) levels in Format |
Paragraph, but of course upon reflection I see that this wouldn't make any
sense; if it were so, then every list item would turn up in the TOC (it's
hard enough to get rid of the "headings" that don't belong there!). I know
how to *use* all this stuff, just don't always understand the mechanics
behind it. <g>

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

"Dave Rado" <dr...@onetel.net.uk> wrote in message

news:#ogsnc17BHA.1956@tkmsftngp03...

[Laura]

Dave,

I just made 3 styles, test1,2,&3 (based on normal) and
then linked them to an outline.

The shift+alt+arrow does NOTHING to them, but if I go into
outline view and try the toolbar arrow keys, they DO
INDEED promote/demote.

This computer has a macro package on it, so maybe that is
interfering with the shift+alt key? Or is it supposed to
be this way?

I guess it's a moot point since I WANT the paragraph
formatting outline levels in them too.

Sigh.

>| >dialog, why is there aÍ{ wÀ j ì¼X5"ga5 "
>
> ì (grayed-out) scroll bar?

[Dave Rado]

Hi Laura

~~~~~~

I just made 3 styles, test1,2,&3 (based on normal) and then linked them to
an outline.The shift+alt+arrow does NOTHING to them

~~~~~~
Works when I try it - in fact I and my users depend on this for all my
outline lists that aren't headings.

~~~~~~

but if I go into outline view and try the toolbar arrow keys, they DO
INDEED promote/demote.

~~~~~~
I presume you must have "Display all levels" switched on in Outline View?
Otherwise you shouldn't be able to see those paragraphs at all in OL View,
if they don't have an outline level.

The toolbar arrow keys are assigned to the Outline Promote and OutlineDemote
commands. Out of the box, Alt+Shift+Right and Alt+Shift+Left are also
assigned to the Outline Promote and OutlineDemote commands. So if the
buttons and the keyboard shortcut are behaving differently from each other
on your system, that implies that Alt+Shift+Right and Alt+Shift+Left are
assigned to something else, on your machine. What does it say they are
assigned to under Tools + Customize + Keyboard? If you rename Normal.dot and
rename the startup path so that no add-ins load, does this behaviour
change?.

~~~~~~

This computer has a macro package on it, so maybe that is
interfering with the shift+alt key?

~~~~~~
Seems like it.

~~~~~~

Or is it supposed to be this way?

~~~~~~
No.

~~~~~~

I guess it's a moot point since I WANT the paragraph
formatting outline levels in them too.

~~~~~~
It's still very useful to be able to promote/demote body-text level list
paragraphs as well, and out of the box, you can.

Regards

Dave

[Dave Rado]

The "Outline Level" is so named because it determines what heading level the
paragraph appears in in Outline View. This terminology made sense in early
versions of Word, which used field-based numbering; but since the
introduction of outline numbering for non-heading styles, the terminology
has cause nothing but confusion. Think of it as "Heading Level" instead of
Outline Level and all becomes clear.

Regards

Dave

"Suzanne S. Barnhill" <sbar...@mvps.org> wrote in message
news:uxOZkJ47BHA.2256@tkmsftngp02...

[Klaus Linke]

Hi Laura,

> For the most part, I was able to decipher what each
> line of the code did... But I don't see WHERE/HOW
> it intercepts the Alt+shift+arrow keystroke.

Everything you do from the user interface calls some Word Command.
You can check what Commands are called by the Alt+Shift+arrow keystrokes in
"Tools > Customize > Keyboard":
The Commands are called "OutlinePromote" and "OutlineDemote".

(For toolbar buttons and menu items, you can hit Ctrl + Alt + Num+ (Num+ =
"+" on the numeric keypad), and then klick on the button/menu item.
This will display the Command/maco and (unfortunately only if it still
calls the built-in command) the keyboard shortcut.)

If the template that is attached to the document (or normal.dot, or a
global template) contains macros with these same names ("Sub
OutlinePromote()" ...), those macros are called instead of the built-in
Commands.
Macros (and other customizations) in the attached template "win" over
macros/customizations in normal.dot, which in turn "win" over those in
global templates.

> I tried to RUN your macro on heading styles and nothing happened.
> When I RAN it on MY styles, it worked. But the keystroke
> Alt+shift+arrow works for EITHER!

Duh... can't see any explanation for that right now...

> And I assume that if I include these macros in the
> normal.dot they'll work in any document on that machine?

Yes... but as a rule, it's better not to put such customizations into
normal.dot.
Instead, put them in a custom template (including your customized Appendix
Heading styles...), and base new documents on that template.

If you want to send the document to co-workers for further editing, send
the template along and tell them to copy the template to their template
folder.

That way, you don't "force" your customizations on other users... and on
other documents ;-) ... most customizations only make sense for certain
kinds of documents.

Regards, Klaus

[Klaus Linke]

Hi Laura,

Just tried it in Word2000, and it did work with styles linked to a list
template (or, for that matter, even with paragraphs where outline numbering
had been manually applied).

It did fail when I tried to demote the first ListLevel-1-paragraph to
ListLevel 2.

The reason is probably that Word assumes a strict hierarchy for outline
numbered lists, so you can't/shouldn't have a list with a missing level 1.

Regards, Klaus

"Laura" <LTow...@stsTrain.com> wrote:

>
> >-----Original Message-----
> You can use as many outlines as you like, and all outlines
> that are linked to styles that have an outline level of
> body text will promote and demote fine. IOW, list
> numbering and list bulleting styles will promote/demote
> fine.
> >
>
>

> Dave -- are you sure? I just tried this in Word 2002 with:
> List number styles that I linked to an outline and that I
> left as they were, styles I created but left "body text"
> level and linked to an outline, and list bullet styles.
>
> None of them would promote/demote by the alt+shift+arrow
> keystroke. I can get an outline to promote/demote, but
> IMO, an outline that is not linked to styles for better
> formatting is a sad thing...
>
> They would either "indent/outdent" but stay the same
> level, or switch to a heading style, depending on the
> circumstances! MADNESS!
>
> Laura
>