My guess is that you've not yet checked the Unique Validation checkbox when you've defined the several PK_ . . . fields.
So long as they are created as UUID AutoEnter Calcs we all kow that they will be unique but I think you will find that FM wants that additional validation to be sure, and before it drops the crow's foot on your RG linkages.
The crow's foot goes all the way back to Version 7 when the RG was introduced, while the UUID function only came with V 12. Obviously the engineers have not yet seen fit to make a PK field created by a UUID function automagically unique.
I hope that helps,
You are right! As soon as I add the unique value the crowsfoot disappears.
The text in the field tab of the manage database screen now reads: "Indexed, Auto-enter Calculation, Can't modify Auto, Unique"
Thanks from the Netherlands!
It is interesting how a Primary Key is designated in FileMaker
This same is true, if you use FileMaker as an xDBC Datasource
> As soon as I add the unique value the crowsfoot disappears
FileMaker has no way of knowing that values can't be duplicated unless you tell it. So it assumes that duplicates are allowed and shows the crow's foot on the key. It should not be taken literally. As this little experiment demonstrates.
The Relationships Graph isn't an ERD and shouldn't be thought of as one.