I have a portal layout on a page. I only want to show the 6 records in
the found set of a "find" in the portal. It is showig me all of the
reocrds in the database instead of just the "found set". How can you
do this?

Thanks
JC Lewis

In article <1130704997.585857.231460 (AT) f14g2000cwb (DOT) googlegroups.com>,
"JC" <jc (AT) jclewis (DOT) biz> wrote:

You can't show just a Found set in a portal. It shows all the related
records, independent of FIND results.

You can create a new relationship based on the FIND criteria of interest.

You can also show the Found Set in a layout based on the related records.

Bill

--
For email, remove invalid.

What Bill says below is basically right and should be followed for all
practical purposes. But I wouldn't be me if I didn't confuse the issue
somewhat. You can write a custom function in FileMaker Advanced 8 that
uses recursion to automatically get all the record IDs for the found set
(using GetNthRecord) and then use a calc field that uses the custom
function to from the "left" side of the relationship that will show the
found set in a portal.


Bill wrote:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Howard Schlossberg (818) 883-2846
FM Pro Solutions Los Angeles, California

FileMaker 7 Certified Developer
Associate Member, FileMaker Solutions Alliance

Since I'm usin FM7 I thought about exporting those records to a
seperate table and showing the portal from that table and then deleting
those records when you're through looking at them?

What do you think?

Thanks
jC

In article <1130711337.877707.194890 (AT) g44g2000cwa (DOT) googlegroups.com>,
"JC" <jc (AT) jclewis (DOT) biz> wrote:

It would work.

You might really want to think about using a layout based on the related
table occurrence.

Suppose your original setup is

A :: B

Where A and B are the two related table occurrences.

You original question was about showing only a found set of B in a
portal in layout of A. As I said before, that can not be done directly.

If you really want to do that, you need to have a new Table Occurrence
of either A or B, and a relationship between them that has the Find
criteria built into the relationship. That can be done, and it there are
sometimes good reasons for doing it that way. For the sake of discussion
call it

A :: B1.

You could have a portal in A showing records from B1, which would be a
subset of Table B based on the criteria built into the relationship.

With FileMaker 7, you can use multi-criteria relationships, so it is
fairly easy to do this.

The alternative, which often makes sense, is to build a suitable layout
in the context of table B. Include such fields as you want from Table A.
Do the Find on Table B, and then you have what you originally wanted,
but in a different context.

Bill Collins

--
For email, remove invalid.

Bill:

Thats more or less what I ended up doing, building some more tables
running scripts to import and delete the records as needed so I could
put the portals on the same layout.

thanks so much
jc

In article <1130790719.256709.244600 (AT) z14g2000cwz (DOT) googlegroups.com>,
"JC" <jc (AT) jclewis (DOT) biz> wrote:

You probably did not need to build more tables and do import & export.
You could have made new Table Occurrences and connected them by
relationships that incorporate the FIND criteria. YOu might have needed
to add some fields to one of the tables to make the relationships work.

Bill

--
For email, remove invalid.