When I print a report of several pages, one of the records on each page will appear to have moved up or down on the page. This puts it out of line with the other records, sometimes cutting off the top or bottom of the text. Preview shows no problem. The same problem can happen when saving to PDF. What is the fix for this annoying problem ?

You've mistaken an "annoying problem" for an "essential feature".

When designing print layouts you can set the sliding/printing characteristics for individual fields. This extends to include sliding UP and LEFT, and relative positioning.

N.B. Theses characteristics don't necessarily show in preview mode - you might have to actually print.

More details in the Help and Manual.

Sliding/Printing *should* display pefectly in Preview mode. Any discrepencies are due to badly written print drivers -- apparently common on Windows platform, rare for Macintosh.

Glenda, what version (and patch level) of FileMaker Pro are you using? The latest is FMP 5.5v2.

[ April 15, 2002, 05:30 PM: Message edited by: Vaughan ]

This is not your Sliding/Printing feature. This is where I have a number of sub-summary layout parts, and the output is a report where several fields are summarised. On the printed page ONE LINE is shifted (printed) lower on the page than it ought to be, and is often missing the top part of the characters (horizontally), or not showing altogether. All other entries of the same sub-summary part are printing correctly. This has happened even when printing a straight list which is not using summary parts.

I am using version 5.0 and have had this problem both on Macintosh and PC.

Glenda: check the FMP version again. What *patch" level is it... v1, v2 or v3? If it's anything before v3 then download the updater from http://www.filemaker.com and install it. It may have been a bug that was fixed.

Do the offending parts have the "allow part to break across page boindaries" option selected?

I've seen similar problems caused by rogue carriage returns and spaces in the field causing unexpected line breaks.

Thanks Vaughan. I have now upgraded from v1 to v3, so here's hoping. So far, so good. Unfortunately this has been a random problem, so only time will tell. But I greatly appreciate the advice.