1 Reply Latest reply on Oct 8, 2012 3:00 PM by philmodjunk

    FMP 11  Starter Solution: Contact Management List view prints only first page

    CliffordEgel

      Summary

      FMP 11  Starter Solution: Contact Management List view prints only first page

      Product

      FileMaker Pro

      Version

      11

      Operating system version

      OSX Snow Leopard

      Description of the issue

      FMP 11  Starter Solution: Contact Management Record List layout prints only first page regardless of how much data is present.  Printing or saving as a pdf has no affect.  Yes, "records being browsed" is selected in the print dialog box.
      My other FMP 11 databases all print normally in list view.

      Steps to reproduce the problem

      1. Select all records.
      2. Navigate to Record List layout.
      3. Issue a P command
      4. Click PDF, Preview or Print in print dialog box.

      Expected result

      Database prints multiple pages.

      Actual result

      Database prints first page only.

      Exact text of any error message(s) that appear

      None

      Configuration information

      none

      Workaround

      none

        • 1. Re: FMP 11  Starter Solution: Contact Management List view prints only first page
          philmodjunk

               I can't reproduce this using Windows XP. I can save a PDF and get two pages. Have you modified this layout in any way? What do you get when you enter preview mode? Can you click the book control and see multiple pages?

               If all else fails, try recovering the file and test the recovered copy to see if it has the same issue.

               Things to keep in mind about Recover:

               While Recover almost always detects and fully corrects any problems with your file...

                 
          1.           The recovered copy may behave differently even if recover reports "no problems found".
          2.      
          3.           Recover does not detect all problems
          4.      
          5.           Recover doesn't always fix all problems correctly
          6.      
          7.           Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.