Portal finds (from article)

[iMarcW]

> Finally, if you perform relational find (thru portal or not) on more than one

> related fields, in other words an AND find, you will get every PARENT record

> (if any) with CHILD records that have ALL requested values but not necessarily

> in SAME record. If you find this "UNEXPECTED", than you are still thinking

> that you were searching for CHILD records.

I just found this out the hard way. It really stinks. Why would anyone want it to work like that?

Since I'm not using FMP 6 yet, can anyone tell me whether "constrain found set" would help in this situation? Search in a portal field, then search in another portal field on that found set, and so on.

Otherwise, I guess the workaround is to create a calculation field that combines the contents of two or more fields commonly searched together, then search on that field for "FieldAFieldBFieldC" in the portal. Good grief.