Fm 12 adv portal inconsistency

[ron G]

I am using FM 12 advanced v 4 in Windows

 

I have a layout based on Members.

Members has a 1 to many relationship with DES table which holds a members Status (Suspended, Deceased, Reinstated etc)

 

 

When I run a report based on the script below, I get "SOME" of the DES records showing whatever is the TOP ROW of the DES portal.  Sometimes, as shown above, I get a different portal row.  (You can see the report showing the single record for Sperry dated June 2, 1997.  It *should* show the top record dated June 9, 2003.  Most of the other records show the top portal row record in the report.  Sperry and Tietjens both show other portal rows.

 

Huh?

 

 

Can you see what is going on?  I m blinded.

 

Thanks

[David Jondreau]

Are your portal and your Sort[] script step sorting by the same criteria (including Ascending/Descending)?

[ron G]

The sorts are the same.  I am still mystafied!?

[Wim Decorte]

in your script you sort by members name and DES date.  You're not in the DES context so can you show us the section of the graph that shows the relationship between Members and DES?

 

As an aside you should adopt a TO naming convention that clearly shows the relationship "path", that makes troubleshooting much easier.

[ron G]

in your script you sort by members name and DES date.  You're not in the DES context so can you show us the section of the graph that shows the relationship between Members and DES?

 

As an aside you should adopt a TO naming convention that clearly shows the relationship "path", that makes troubleshooting much easier.

 

Yes, my naming convention sucks.  I am writing this app as a 'free' learning experience for a non-profit.  So I learn as I go....

[ron G]

 

I show all records.  I notice that Mason and Myer and conecutive members.  So, why does {{RecordNumber}} skip from 40 to 42?

 

 

[ron G]

Here is a pdf of the report as run.

 

Dues by Dues Status.zip

[bruceR]

The report is behaving as expected.

 

You put the record number indicator in the subsummary part.

 

So when you get to Kemble (33) who has two payments (records 33 & 34) , then go to Kerby, his payment record is #35.

[ron G]

Yes it is.  I can see that when I step through the report it is going from one record to the next record IN THE CHILD record.  I finally took the easy way out and based the report on the parent MEMBERS and put a simple 3 line portal based on Dues.  Now i just have to get the Sub Summary fields for each Current and Late Section working.... Thanks for your help.