I'm struggling with a Join structure which depends on an unstored calc. It may be that all I need is a script step to force the recalculation of the unstored calc.

Here's the current structure for the Portal:

Companies table|Contacts table

Company ID = CompanyListAll_calc

The unstored calc field has this formula: "¶" & List ( Contacts~JOIN::_CompanyID ) & "¶".

The Contacts~JOIN TO has this structure:

Join table|Companies table

Company ID = Company ID

When I open the CompanyListAll_calc field to examine its current storage settings the field recalculates and the missing record suddenly turns up in the portal as needed.

Is there a better way to structure Joins, or do I just need a script step to refresh that calculation?

I don't see why you need to use the List() function for this. If you go thru a join table, you will see the many related records of the Contacts table.

From Company to Join:

CompanyID =Join::CompanyID

From Join to Contact:

Join::ContactID = Contacts::ContactID

From Company thru Join to Contacts, you'll see the many contacts attached to that company.

You might need the List() for something more complex and esoteric, but not for this.

BTW, you don't need a leading and trailing ¶ for a relationship; it doesn't care. You often use that construction when parsing from or substituting within a list, in order to ensure you're matching an entire line; but it's not needed for relationships.

Fenton, thanks for this. So simple. What's going on here is an artifact of FMP6 thinking.

Much appreciation.