I’m having problems with mergefields in a single document header, in a document which contains several sections (therefore, several headers). Let me try to explain clearly:
The document contains three sections. Section 2 is continuous, so its header/footer do not appear. Section 1 and 3 headers are slightly different, but each contains two mergefields — the exact same two mergefields. No first/odd/even headers and footers are used.
Section 3 consists of an INCLUDETEXT field to draw in a separate document, and a bit of following text inside a frame. The separate document has no header and footer; those are being controlled by the first document. The INCLUDETEXT actually also contains a mergefield, because the separate document is not the same every time — the mergefield brings in the correct path to the separate file, and that appears to be working splendidly.
When I merge the document, the fields in the Section 1 header work perfectly, I get the data I’m looking for. However, the fields in Section 3 header do not merge at all. In fact, they come out looking like unlinked mergefields with no data. Something like <>.
The crowning bit of weirdness: the merge document is being set up to run as part of an automated process, so the merge will actually be run by a macro. The tests I run through the macro show this result. But if I merge the same documents manually, with the same data, all of the header fields work perfectly. No problems at all.
Sigh.
Has anyone seen behavior like this, or have any suggestions what I might do about it? Thank you!
)
