Difference and Reasoning behind using the two different TOC styles

[lsk2002]

Good Morning,

Since there are two ways to make a TOC:

a. Add TOC

b. Special TOC for document

Our component manuals have a cover, toc, body, and back cover.

Our product manuals are set up by section, and have the toc, and body. Of course a cover and back cover.

So my question is what is the difference in using one or the other toc:? We also have to have bookmarks and links in the toc?

Just thought I would get the real reason behind which one is used for what.

Thanks,

LS

[Arnis Gubins · Accepted solution]

Functionally speaking, there is no difference. They both work the same. It's the scope that varies.

If you have a book, then use the first approach (add the TOC). It will scan all files in the book and automatically update when you re-generate a book.

Creating a stand-alone TOC is a convenience that in the past has been used for various purposes (such as embedding mini-TOC's in a document) that can now be more easily done with the new functionality in FM2015. The stand-alone document TOC has to be run manually to update.

[lsk2002]

Yes, that is what I don't like about it, though if you have a book with sections and section toc's, I guess there isn't a choice unless a mini toc can be produced.

I was just wondering if there was any other reason behind the two.

Thanks!