Hello, we're using 5.5 and are still vexed by the situation described above.

There used to be (versiion 3!) a crafty option-key move that would supposedly fixt this problem... but it was never a complete cure.

We keep our correspondence in FMP using calculated header material (cc lists, addressing, etc). Are the calculated headers, plus all the sliding/shifting just too much for FMP to handle? Are there any workarounds other than manually ***grrr*** previewing and adding paragraph breaks to make lines avoid the page break?

Have you defined 'Fixed page margins' on your print layout? - that should fix most half line breaks. FM will have problems printing portals across page breaks - portals were not meant to be printed.

If you can setup your print layout to use a single, large text block and merge fields, your printing will be more predictable and will break correctly.

hmmm.... are you really saying that *if* we always print from single, large text blocks then we will *never* get chopped lines?

if so, that would be fantastic! I'll have to look at our layouts and see what can be done... they tend to be kinda complicated, what with rules and portals and such.

but no: we haven't defined "fixed" margins from the layout settings. I'll look into that.

Notice that DykstrL said as "merge" field(s). They print much better than regular field blocks, as they are designed for print.

Yes... single large blocks of text assembled from merge fields, right?

I have a couple of applications that create custom letters and print them. In these I run a script that combines field data, predefined sentences and paragraphs into a single global text field. The letter print layout contains a title header, regular header for page numbering, and the body contains a large (up to 5 pages) text block with the global field entered into the text block as a merge field. The text block is set to slide up and shrink. The layout has set margins of 0.5 all around. The script allows the user to preview the letter before printing it or going back to revise the letter data.

This setup has yet to produce a chopped line.

Hey guys - another issue has cropped up ;-)

I have taken one of our layouts and assembled it into one massive (or actually, quite tidy by comparison) merge field for printing our letters.

However, paragraph formatting unique to a record does not appear in the the merge field. The merge field seems to know only about it's default format.

Any way around this? I need record-specific formats to come through...

Thanks for any help you can provide.

On edit: just thought I'd add that specifically what doesn't seem to stick is *tab and paragraph settings*.

FM help file says:

"If you use a text field as a merge field and specify text attributes (like style, color, or size) for that field's value in Browse mode (on another layout), the merge field picks up those attributes."

Other font-formatting does indeed transfer in this manner. Tabs don't appear to...

Have a look at this link.

http://www.fmforums.com/threads/showflat.php?Cat=0&Number=1518&an=0&page=2#1518