And what Notes field is that? Could this be a large text field with multiple entries in the same field? It's usually a better design to set up a portal to a related table of notes so that each note entry is in a different portal row.
For printing, you can set up a list view layout based on the Notes table and still be able to include fields from the parent record in the layout. This can be pretty flexible in terms of the amount of data included in the notes.
But that option doesn't always work for every situation, and then you are back to using a very large portal set to slide/up reduce--which won't be terribly different from using a very large single note field set to slide up and reduce the enclosing part.
Key facts about sliding layout objects:
- It's only visible in preview mode and when you print/save as PDF...
- Sliding fields will shrink but not expand.
- All layout objects below and in the same layout part as the slide/resize field need to also be set to slide up and resize.
- Objects in headers and footers will not slide.
- Portals will shrink/slide to fit the number of rows of records, but fields within the portal row will not shrink/slide.
- Fields will slide up only if Top alignment is specified for it and will slide left only if Left alignment is specified.
- Consistent side borders are difficult to achieve with sliding fields.
- In FMP13, hidden objects (”Hide object when”) will slide/resize.