Hi CyberTas,

If Robert converted all his INCLUDETEXT fields to RD fields, *ALL* the
individual chapter headings would apear as 1, 1.1, 1.1.1, etc in the ToC and
page numbering would restart at 1 for each Chapter.

Adding a {SEQ Chapter \r#} to EACH chapter (substituting # for the actual
chapter number) and using {SEQ Chapter \c}-{Page} for the page numbering and
adding \s Chapter to the {TOC} field inthe "Master" would resove the page
numbering but not the Heading numbering.

Any clues how to get the TOC to reflect 37.1, 37.1.1 etc for the heading in
Chapter 37?

Cheers,
Gerri
--
Gerri, Tech Writer
Australia


"CyberTaz" wrote:

Hi Robert-

If the doc size is that large and would contain many embedded docs, you
might be better off to create the finished product as a PDF... Especially if
the users are not expected to edit the file.

Regards |:)


On 6/15/05 11:53 AM, in article ,
"Robert M. Franz (RMF)" wrote:

Hi Callanish

Callanish wrote:
Sorry, I'm not explaining myself too well! This is what I mean:

1) Insert Object
2) On the Object dialog, select the "Create from File" tab
3) Check "Display as Icon" box, then Browse to the file, and OK

The main document would be a top-level summary document, containing the more
detailed design documents (inserted as above).

Do you think this is a completely mad thing to do? It's not my idea, I'm
just the technical writer! ;-)

OK, I see what you are doing. What is the ultimate purpose of this
document, BTW? Internal usage? Sending off with the product to the
customers?

I would not do it with objects. Inserted objects like this look rather
tricky to me, esp. when you imagine the lifecycle of such a document;
whether it should work on systems with different earlier and/or later
versions of Office installed, too, for instance.

If you really want to have a kind of "table of contents" document
(instead of bringing the content together in one file [directly, or via
INCLUDETEXT fields]), I'd try RD fields.

Greetinx
Robert

--