Hello.

I have prospect database and a next-action related file in FMP 5.5.

NextAction file has DateCreated, NextActionDescription, DateDue,
CompleteStatus (yes or no), DateCompleted

I want be able to search in the NextAction portal and constrain the
found set to those records in Prospects that match the criteria.

The problem is that seaching in the Portal seems to be a "OR"
search.

For instance, if in find mode I put "Phone Followup" for
NextActionDescription and "No" for CompleteStatus, I get all the
records in Prospects that have a related record in NextAction that is
"Phone Followup" OR "No" in CompleteStatus.

I want just the Prospect records that have not been called yet!

I tried this in 8.5 and it seemed to work as I expected. How do I do
this in 5.5?

Thanks a bunch.

Darren Burgess

"Darren" <darrenburgess1967 (AT) gmail (DOT) com> schreef in bericht
news:1175105006.866503.290620 (AT) d57g2000hsg (DOT) googlegroups.com...
Darren,

I think you have to create a calcfield. This has the Description and the
Status put together:
cRel <Text; CompleteStatus & " " & NextActionDescription>

then on the other side of your relation also create Calculated key, made
from the search options, in a similar fashion as the first field. Then
relate these two fields and use the relation for your search portal.

Keep well, Ursus

In article <460ab9d7$0$201$dbd41001 (AT) news (DOT) wanadoo.nl>, "Ursus"
<ursus.kirk (AT) wanadoo (DOT) nl> wrote:

You can't have Calculation fields on the child side of a relationship
because they can't be indexed. You could use a normal field with an
auto-enter calculation, but that throws up other problems (for example,
changing CompleteStatus to "Yes" won't change the auto-enter
Calculation ... at least not in FileMaker 5.5 being used in the
question).

Technically you could create the Calculation field in the NextAction
file and then add that field in the Portal of the Prospects file, but
it makes a messy portal with extra fields that are only there for
performing Finds.

Performing a Find through a Portal isn't really a good idea. As you've
discovered it doesn't work as expected, and often (although not this
case) this is caused by people not understanding the results - a Portal
always displays ALL related records, not just those related records
matching the Find just performed.

It would be better to perform the Find in the NextAction file (using a
relationship link back to the Prospects file to retrieve any needed
data) and view or print the results from there.



Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)