You can create another table occurrence of work_numbers. You will also need an unstored calc that just returns '1' on the parent side. You can now have the relationship to be keyed from this calc field to your boolean field in work_numbers (2). Now have your value list be based off this relationship.
You will also need an unstored calc that just returns '1' on the parent side.
Well it doesnt HAVE to be unstored but why would one store a simple constant calc field? The user could use a global calc as well but the overhead is just as simple as an unstored calc...
...but why would one store a simple constant calc field?
To never need that FileMaker makes a recalculation ?
To have a bi-directional relationship ?
BTW: I only wasn't sure to why you made that precisation.
I too would make it an unstored calculation. I cannot see that the 'opposite' relationship would ever be needed, and recalculating "=1" is negligible compared to storing "1" in who knows how many records.
Another option is to define a calculation field =
Case ( Active ; Value )
and base the value list off this field. This eliminates the need for a relationship to filter the records.
Sorry I'm a little slow here. How do you get the "1", and what do you do with it then?
PS I new at this.