Is the parent record COMMITTED after the delete portal row? Does that make a difference?
Yes it is committed. The index values I'm looking at are in the child table. I don't think it would matter if the parent record was committed or not. What is odd to me is the record was deleted but the index values weren't updated.
It's a data separation model, i.e., the actual file containing the user interface is not the one housing the actual parent record table?
If so, I've seen that kind of misbehavior. Employer had me design a relationship-driven selection screen and meanwhile had a second developer doing other things that resulted in a design decision to eliminate the parent table entirely in favor of a similar table in another file. Values that were no longer related were still showing up after selection criteria had been chosen, while the truly related values did not show up. Some kind of lag in the update of the index, as if it were being cached in the front end file.