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?