Hello everyone,
I just need help!! I feel like I'm drowning in Word Multilist world, I have spent the last 4 days getting my document with all the same multi-list style, and I'm about to lose my mind!

Background (My Word Story)
I have a document that I compile out of 20 different Word Documents, Chapters. We take all the Chapters and combine them into one Huge document (It's up to 1000 pages). My users go in and made edits, paste etc in the chapters and I combine them. All the chapters have the same Styles so that everything looks the same. (Or at least I hope so). But when I compile the document the multilist goes haywire! totally nuts!!
So my Heading 1, 2, 3, 5 do not have numbering on them on purpose. But my users use "List Style" and that List style is attached to the built in Multilist style in word. (Sample 1., a, i, 1, etc). The users are good about sticking to the styles.
But when I combine them it gets crazy.



What would you do? I tried to manually correct each one that that's almost impossible, I got up to Chapter 15 and it stared to get worst.

I read that maybe a Macro would help, so I'm guessing a macro that finds all of the "List Paragraph" and changes the Multilist.
1. Is this possible?
2. Can some one point me in the right direction?

I"ve used Shuana Kelly site which is great but I think I'm beyond this.

Drowning slowly in Word Number list!

I don't know how to answer your questions using that poll. The answer is yes to all of them. If you have been reading the late, great Shauna Kelly's site then you have the basics down so that is a good knowledge base.

Multi-level lists have a number of gotchas but they can be made to work well if you have some macros to assist when/if things go wrong. If your users are good at sticking to styles then you can solve all issues with the macros and being ready to remove local formatting.

You should start by having a template which has defined the styles the way you want them. Then attach that template to all docs and refresh the styles to reflect the style definitions in the template. This makes the combination into a single document much more painless.

List Paragraph is an issue though because sometimes people intend for those to be bulleted lists and sometimes numbered lists which is an inconsistency that makes things harder.

I will ask though - is there a reason you need to compile all the documents into a single document? What is that reason? It might make sense to keep them in separate documents if there isn't a compelling reason to combine.

__________________
Andrew Lockton
Chrysalis Design, Melbourne Australia

@Guessed - Thank you!!

This is actually a Product Requirements Document that we put together. Each Component is divided into each Chapter, there are currently 20 components as the system grow we add chapters. We update this document quarterly based on Change Requests for the System. So lets say in Chapter 3 there is a change, we make those changes in Chapter 3 ( and show Track Changes) and then compile it once that change is implemented in production. The compile document serves as what the Product is at this given time.

This may be an older way of doing this? Would like to know how others handle this?

It is a valid way of doing things but you could also consider keeping the files separate and using different strategies to make compiled files. If you are having problems only when you merge docs then it can be easier to just keep them separate. If keeping separate you have few options:
1. Using RD fields to build TOCs and/or Indexes. Output docs to a combined PDF version for current versions.
2. Use includetext fields to import the current versions of the parts into a single doc
3. Use Master Docs feature and be careful to ONLY edit the separate chapters as standalone docs.

Options 2 and 3 might require you to structure your multi-level list styles a particular way so the merger doesn't make separate lists continue numbering. I would need to see your docs to give more detailed guidance on managing the lists so they work correctly in standalone and merged modes.

__________________
Andrew Lockton
Chrysalis Design, Melbourne Australia