three flows defined, mysterious hiccup in two of them

[Guest]

Baffled, I am, quite baffled! I set up a new document with three flows (A, B and C – why not) to handle parallel texts in three languages. The first four pages work like a charm, including some very satisfying autonumbering; and then, at the top of page 5, flow A and flow B reset their numbering while flow C plods happily on as expected. Worse than that, flows A and B pick up the "real" numbering again – on page 6!

Question 1: what am I doing wrong, and how do I correct the mistake?

Question 2: once I've finished the three column/three flow part, I need to add a final page with a single full-page flow. Should I set up a master page with a new flow, or continue from one of the existing flows and change the column definition?

Thanks in advance for help on this challenge.

N

[ps] just spotted that when I check the master page for the three-flow layout, there's no visible frame for flow A. Related or coincidental? I've had other documents where frames didn't show.

[Arnis Gubins]

If the three flows are defined on the Master pages and all have the proper autoconnect option enabled, then ot should theoretically be working. However, since you indicate that the the text frame for flow A is missing on the master page, then FM might be getting confused. Is the text frame actually there on the Master page (ctrl+A to select all objects) ? If so, then check the frame properties and re-apply master pages.

Note: I've also had issues with FM and multiple flows, especially when filling content in flows other than "A" first. FM seems to be easily confused confused and does its own thing in these situations.

[Guest]

> Is the text frame actually there on the Master page (ctrl+A to select all objects) ?

No, which is a bit strange; on the body pages, a flow shows up where expected and (according to the status bar) it is indeed flow A.

Drawing a new text frame and assigning it to flow A seems to do the trick, though, and thank-you very much for the tip. I suppose I should also be grateful that FrameMaker got as far as it did with loading text into a semi-non-existent container <g>