I'm using a calc field with a container result to highlight the current portal row. When the user selects a different row a script sets the ID from the related portal record to a field in the current record. The calc simply uses an IF and when the ID's match the result equals a global container that holds the hilite color.

The problem is that the last portal row highlights in addition to the current row. I understand that if I uncheck the box that allows record creation it doesn't do it anymore, but I want to be able to create records from the portal. Is there a workaround that will keep the last row looking normal without disabling record creation through the portal? I've tried making the calc field not a button and even reversing the calc to display white when true and highlight when not true, but that last row highlights no matter what. I think it's similar to a button always showing up in the last row. Any help much appreciated.

Thanks.

Put your calculated container field in the related table, change your relationship to reference only the related TO, and have your script set a related global with the ID. Then put your related container calc in the portal.

Got it! Thanks. It was moving the global ID to the related table that made the difference. Of course this looses the stickiness of the selection in each record.

The conclusion is, the last line highlights when the calc references a standard text field in the parent, but does not highlight when the calc references a global in the related (portal) record. Still looking for a tighter implementation, but there is another gotcha... The highlight doesn't work if the cursor goes into an editable field. So I think the best implementation is to use the permanent key in the parent, turn off the ability to add records through the portal, and set the portal fields to not be accessible in browse. This will require another layout to add contact names, but that seems smoother than having a glitchy portal implementation.

Thanks a bunch for the insights Queue.