Is there a way to 'make' FM read the top row of a portal?

[ron G]

I have 2 tables Members->>DES

 

DES is a portal on Members.

 

I have a report based on Members in which I need to pick off the top row of values in DES.  (It is sorted Descending by Date)

 

In my report, when I specify DES::Date, I do not get the top row of the portal.

 

I think I can set up a 'scratch' field that will hold nothing but the current date and write to it when I input the date, but the question is  "Is there a simple way to make FM recognize the top row of a portal and when the report sees DES::DATE it pulls up the TOP portal row DES::Date?

 

 

[Raybaudi]

Try to sort descending by date the relationship: the first row value will be DES::Date

[ron G]

Try to sort descending by date the relationship: the first row value will be DES::Date

I had sorted it at the portal level by DES::Date but *not* at the relationship level.

 

Doing so at the relationship fixed the problem.

 

Correct me, if you will, it was my understanding that abasent a SORT at the relationship level, then the SORT at the portal would dominate.  Apparently not.  Can you give more information on where my understanding is wrong?

 

Thank you!
 

Ron

[Raybaudi]

The Sort at the portal level makes ONLY a visual effect, so ( in absent a SORT at the relationship level ) your DES::Date isn't the first portal record but the first created related record.