new records addded to table not included in portal

[kmhappel]

I must be losing it! I know this is so simple that I am embaressed but I am mind dead about this. I have a portal that has worked perfectly up to now. It was originally a const1 type self join. The portal is now using a single key matched to a multi-value selector list of values delimited by a carriage return (so I can filter portal entries by a first letter in a name etc.). All the records show proper match field contents. The current problem is caused when I create a new record on a layout dedicated to the original table instance. The new record doesn't show up in the portal even though it has a proper match content. Switching layouts, sarting and stoping the program, saving copies, executing scripts helps not at all. The record exists and if I go to a different layout that displays the exact same table but without the portal the record CAN be found. Menu: Records: Show All Records doesn't help on any layouts. All preexisting records function perfectly. The record, if selected in the nonportal layout, even shows up in the fields of the layout that the portal is in but not in the portal itself. The number of records in the status area shows fewer records than the other layout. I've tried mode changes, finds and all kinds of things... Yikes help! I've lost it.. mumbling sadly in San Diego...

[crebma]

i am having the exact same problem starting just last night! but i'm using fmp 7. strange!

[kmhappel]

Solution... Relationships 101 mistake... Well I knew that I knew... The match field was a calculation that included a reference to a nonindexed field as so it, also, could not be indexed... and you can't match a key with an unindexed field in a relationship.

The referenced field used to be indexed but in a revision it was changed making the entire reference chain fail the indexing test. All better now and no longer sadly muttering in San Diego. It is crazy how long I looked at that thing before I got it.

Hope this helps you too, crebma... check if some change in a calculation or reference that is part of the match field has made itself un-indexable.... Old records still had index inside somewhere...

Edited October 26, 2005 by Guest