AnsweredAssumed Answered

Page Break bug

Question asked by tonyduffy on Nov 28, 2010
Latest reply on Nov 29, 2010 by tonyduffy


Page Break bug


FileMaker Pro



Operating system version

Windows 7

Description of the issue

I'm creating a report layout for a staff roster which is often updated, necessitating the deletion and import of records from another FM database. The layout contains fields, in order: staff member name; day of week; date, (the layout is grouped by staff member name and date, so all three are positioned in a sub-summary above the body); concatenated start and finish time field; client name , (these last two fields are in the body of the layout).

I need a page break inserted with each change to the staff member name only. When I first create this report, the page break works fine, separate page in each preview. However, as soon as I make changes to the records, including deleting and importing, the page break ceases to function, despite the part still showing up in the layout and part setup. The page break never functions again unless I create a whole new layout and then it only works until the first change in record entry and not again after that.

Steps to reproduce the problem

I have recreated the report several times and with several variations, including grouping by just the staff member name and not the date as well. The same situation still exists no matter what I try.

Expected result

Page break for each data change in the staff member name field.

Actual result

Works only until there is a change in the record or until the database is exited. After that the part remains in the layout but the page break will not function. Given that the page break works on creation and first use of the layout but subsequently and irreversibly stops working, the only conclusion I can come to is that the issue is a bug in the FM program itself.

Exact text of any error message(s) that appear



None. Everything I've tried, grouping by one field only, moving grouped field(s) to header, sub-summary or wherever, even making a copy of the staff member name field and sorting from the copy, still comes up with the same problem.