With that relationship, you will need to use at least one portal to list either Visits or Members. The portal will need to be set to be many rows taller than you ever expect to need and then you set it to "slide up" resize enclosing part to shrink it down to just the number of rows needed to display all the data.
There are limitations to this approach that can be frustrating, but it's the simplest option to try first. Other options would require importing both Members and Visits data in to the same special "report table" so that you can set up a list view layout based on this report table--that can open a major can of worms but you can often produce results not possible with portals.
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.
Thanks for quick response. I used to portals one for household members and one for visits. Resizing not optimal but adequate for my needs.
You can reduce this to just one portal if you base your layout on either visits or household members. In such case, you need only one portal for the other of these two tables. That sometimes provides some better layout options as you'd use list view to display the data for one table and a portal for the other.