I have a portal populated with potentially thousands of rows, and I want to print it out for the user. I tried forming a new layout (just for printing) consisting of a very large body part, cramming as many rows in as possible - but it's much too limited, and I can't take advantage of "sliding". I've hit upon something that works, but it seems terribly clumsy. I'm hoping someone can tell me something more direct and elegant using FileMaker as it's supposed to be used.

Basically, I defined a new table consisting only of a key field, relating this table to the portal's underlying table using the key. I insert rows in the new table for each portal row in the underlying table...and then I can nicely print the rows using the new table as a basis. The way I populate the rows in the new table is to loop through the portal, forming a string of keys separated by blanks. Then I loop through that string, adding rows in the new table for each of those keys.

I've wracked my brain trying to figure out a direct way to accomplish this, and this is the best I've been able to do. It has the advantage that it works, but as I say, it seems like a clumsy hack. (I should add that the portal is formed via a complex multi-table relation - no simple find will do.)

I'm steadily learning FileMaker techniques - and I'd sure like to learn a new one here!

Print from the related table using a columnar list/report layout.

Thanks - but without a portal, this approach only gives me a single row in the report. And (as I mentioned in my post) if I use a portal, there are unacceptable limitations.

What am I missing? This seems like it ought to be so simple.

If you are using a columnar list/report layout you will get as many rows as you have records in the found set. This layout uses the related table. Go to the related records show only related records using the layout report. This find the related records, the ones in the portal, and will give you a report that displays every line that was in the portal. It can be more than one page.

My problem is, Ralph, that I don't seem to have a "found set".

Picture this: I have a layout based on a "Criteria" table I use for matching. This table has a single row with fields that correspond to fields from another table - call it the "Data" table - from which I want to retrieve data. I can click on checkboxes in the fields in my "Criteria" table to change the match criteria. The layout has a portal where matching records come in from the "Data" table. As I interact with the layout, checking and unchecking checkboxes, the portal is changing immediately and automatically. The found set of the "Data" table is not changing, so I can't use a found set for printing.

Or at least that's how it looks to me.

Furthermore, I'm not smart enough to transform the above portal into a found set.

I do very much appreciate you trying to help me out!

Rick

All you need to do is go to related record using the same relationship that you are using for the portal. Show only related records. This will produce a found set that amtches your criteria.

You are smart enough to do this.

Ralph - I've had this percolating for some time, bugging me. Last night, I made the conceptual breakthrough I needed for me to comprehend the simple approach you were trying to explain to me. I didn't understand enough about Found Sets and how to create them.

Using Filemaker as it was meant to be used simplified my approach tremendously, and it's also much, much faster.

Thanks for being patient with me. I may be "smart enough"...but I also needed a paradigm adjustment.

Rick