My database is a job log of graphics work. I want to display an overview via a self-join relationship in a portal. The match field is complex, a calculation field with the form:

abc

where

a is an autoentered value which the user can update (it flags up when a job is completed and can be archived)

b is a calculation based on whether the start date is < get (CurrentDate).

c is a required entry from the user when they create the record (it puts jobs into a category 1-4 dependent on type, eg. flyer, leaflet etc)

I have the relationship set up such that the self join is between the dynamic abc value, and a global abc (eg. abc=global_123).

My problem is that, whilst the abc values are correct, they don't appear in the right portal. I can verify this by adding the abc fields to the portal layout. For example, I've got a portal set up to contain only abc=234 values. It does contain all of these, but also a 224 value. And that 224 value doesn't appear in my portal set up to contain 224 values (but other 224 values are there).

What could be happening?

You cannot base a relationship on unindexable fields on the child side. Your ( part uses Get(CurrentDate), so I am guessing that's unstored.

BTW, in version 7/8 you can use multiple criteria for a relationship, instead of concatenated calcs. One of the criteria can be that child's start date is < parent's global/calc date.

Thanks, that works great! This is the first time I've used FM since v5, very impressed with the new features.