Having portal issues

[oscarbum]

We are using portals to track our theatre ticketing history. We have it set up so that the most recent order appears at the top of the portal. However, when anyone tries to pull a report than involves any of the other portal rows, it finds the correct patron and puts it in the report but posts only the info from the top portal row. The info in the portals is kept in a separate FM document and each portal row has its own order id number. Any ideas on how to fix it? I have a feeling it's something really simple I'm overlooking.

[-Queue-]

Is the report in your parent file or the child (related) file? How exactly are you selecting the related record for the report?

[mattlight]

This appears to be very simular to my problem which I've just posted - keen to hear the answer to this.

[oscarbum]

The answer was actually in the design. Since most of the data in the report was in the child file, but the report was in the parent file, it was basing everything on the parent info (which was static) as opposed to the child (which always changes.) I rebuilt the report in the child file and the problem was solved. Thanks.