Oh sorry ... I must not have turned on auto notify!
Anyway, that was the exact article I found that gave me the idea to split
them up. Thanks Stefan & Suzanne!--JT
"Suzanne S. Barnhill" wrote:
Shauna has an article about a similar use:
http://www.ShaunaKelly.com/word/glossary/glossary.html
--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
http://word.mvps.org
"Stefan Blom" wrote in message
...
That seems like a clever workaround!
--
Stefan Blom
Microsoft Word MVP
"JT Klipfer" wrote in message
...
Hi Stefan--Thanks for letting me know. I've found a way around this by
making my acronyms indexed entries and my definitions TOA entries. Not
perfect, but it gets the job done! Thanks again.--JT
"Stefan Blom" wrote:
You can't control which styles are being used for the index entries. In
a
run-in index, all entries use the Index 1 style; in an indented index,
Word
applies the appropriate Index style (Index 1, Index 2, and so on, up to
Index 9) based on the level of indentation.
--
Stefan Blom
Microsoft Word MVP
"JT Klipfer" wrote in message
...
Hi,
I have a rather large document in which I'm creating two indices: one
for
acronyms {\f "a"} and the other for definitions {\f "d"}. I'm using
the
\t
switch to contain either the acronym description or the word/phrase
definition, since I don't really want page numbers to show. The
problem
however, lies in when I try to apply different Index styles to my
{INDEX}
field.
For the {INDEX \f "a"} acronym index, I've chosen an indented index
type
so
that the acronyms & associated descriptions appear in a columnar
fashion;
I've modified Index 1 style to meet this desire.
But for the {INDEX \f "d"} field, I've tried to do a run-in type of
index
and I've tried to click the Modify button to choose Index 2 style, but
I
can't seem to get that selection to stick. Somehow it keeps
defaulting
back
to Index 1, which is formatted for my acronym list.
I have found a workaround by manually reformatting my definitions list
with
my desired formatting and then locking the field. But this really
sort of
defeats the purpose of automating it all. Any help would be greatly
appreciated!
--JT
.
.