+ Reply to Thread
Results 1 to 6 of 6

Portal not showing all related records

  1. Portal not showing all related records

    Using FM 8.0v1.

    I've got a problem where a portal is not finding all of the related
    records - I can search for the information in the match field and turn
    up 11 records, for instance, but only 4 will show up in the portal.

    To be more specific: I've got one table titled "Individuals", and
    it's got one record per individual, with the Individual ID and the
    Nest ID. I've got another table of Nest IDs that lists the mother and
    father for that nest. This relationship is working fine - a portal in
    Nest ID shows all of the individuals from that nest, no problem.

    What I want is to be able to call up an individual and find all of
    their kids. The way I'm doing this now is to create a field in the
    Individuals table called "Mom" (or "Dad"), and use a calculation to
    pull the value from the Nest ID table. Then, I've created a duplicate
    table called "Mom Individuals", and it matches the Individual ID from
    to the Mom IDs. Creating a portal based on this relationship gives me
    a list of all the individuals for whom a particular individual is
    listed as a mom.

    ....or at least it should. It's not turning up all of the results that
    I can get if I search within the "mom" field, and I can't see what's
    different between the results it does and doesn't turn up.

    More worryingly, within the portal for all records with ANY offspring
    (using a *) turns up a whole lot of records where the portal fields
    appear blank (although there should be something there).

    Any ideas on what's wrong and how to fix it? Or an easier way to set
    up this two-step relationship?


  2. Re: Portal not showing all related records

    Make sure all the fields fit inside the first portal row.

    Keep well, Ursus

    schreef in bericht
    news:c3c23ec7-5551-4057-89a3-ed35d1940f10@2g2000hsn.googlegroups.com...
    > Using FM 8.0v1.
    >
    > I've got a problem where a portal is not finding all of the related
    > records - I can search for the information in the match field and turn
    > up 11 records, for instance, but only 4 will show up in the portal.
    >
    > To be more specific: I've got one table titled "Individuals", and
    > it's got one record per individual, with the Individual ID and the
    > Nest ID. I've got another table of Nest IDs that lists the mother and
    > father for that nest. This relationship is working fine - a portal in
    > Nest ID shows all of the individuals from that nest, no problem.
    >
    > What I want is to be able to call up an individual and find all of
    > their kids. The way I'm doing this now is to create a field in the
    > Individuals table called "Mom" (or "Dad"), and use a calculation to
    > pull the value from the Nest ID table. Then, I've created a duplicate
    > table called "Mom Individuals", and it matches the Individual ID from
    > to the Mom IDs. Creating a portal based on this relationship gives me
    > a list of all the individuals for whom a particular individual is
    > listed as a mom.
    >
    > ...or at least it should. It's not turning up all of the results that
    > I can get if I search within the "mom" field, and I can't see what's
    > different between the results it does and doesn't turn up.
    >
    > More worryingly, within the portal for all records with ANY offspring
    > (using a *) turns up a whole lot of records where the portal fields
    > appear blank (although there should be something there).
    >
    > Any ideas on what's wrong and how to fix it? Or an easier way to set
    > up this two-step relationship?
    >




  3. Re: Portal not showing all related records

    I checked this, and sadly it doesn't appear to be the case.

    Any other thoughts?

  4. Re: Portal not showing all related records

    I checked this, and sadly it doesn't appear to be the case.

    Any other thoughts?

  5. Re: Portal not showing all related records

    In article
    <7ce3b2a2-4035-4bdc-831a-abebadfb6c1b@a1g2000hsb.googlegroups.com>,
    NickiG wrote:

    > I checked this, and sadly it doesn't appear to be the case.
    >
    > Any other thoughts?


    When a Portal is not showing the expected records then there's only
    really a few options for what can be wrong and you need to carefully
    work through a list:

    - the fields are not inside the portal rows boundaries

    - the fields and / or Portal are using the wrong Relationship
    (if the fields in the Portal are using a different
    Relationship to the Portal, then you'll get some very
    peculiar results - this is very easy to do, especially
    when using simiarly named Relatiosnhips)

    - the fields in the Portal are the wrong fields
    (eg. Calculation fields that are calculating as empty,
    which means the rows look like they aren't there when in
    fact they are)

    - the Relationship is set-up using the wrong fields or wrong
    type of fields (a Relationship will not work if the Child
    side is a Global field or a Calculation field)

    - the Relationship is set-up using the wrong Table / file

    - the data in the link field is wrong, either at the Parent
    end or the Child end (eg. perhaps multiple Child records
    have the same data "Fred" when some of them should be
    "Freddy", or some are "Freddy" when they should be "Fred")
    Note: The display formatting options for the fields are
    irrelevant to the Relationship. Change the field formatting
    options on a Layout for the fields to "Leave ... formatted
    as entered" or "General format" so that you can see the
    actual data FileMaker is using for the Relationship link
    (eg. "30/6/2008" is different to "30 June 2008").

    You might also have problems if there is more than one copy of the file
    on the computer (or even on the network), according to FileMaker Inc.
    anyway. I can't say I've ever run into this problem myself - maybe it's
    a Windows only problem.

    That's all of the reasons I can think of at the moment, except the much
    less likely option that the files / Table has become corrupted or is
    having Indexing problems. For this you may need to use the Recover
    function and then import the data into FRESH backup copies of the file.





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

  6. Re: Portal not showing all related records

    wrote:

    > I checked this, and sadly it doesn't appear to be the case.
    >
    > Any other thoughts?


    I think it would help if you described the problem further.

    How many rows should be shown? How many rows are shown? Have you given
    your portal a vertical scroll bar?
    --
    Per Erik Rønne
    http://www.RQNNE.dk

+ Reply to Thread