I am a new user having a problem with my first FMP DB. I think what I want to do based on what you have shown here is auto assign a UUID to the PF of my parent tables, and leave the FK in my child tables blank. Since the UUID code contains that long random string, I never want to see the contents of the Parent PK anywhere, or search using UUIDS to relate my Child FK fields. For reasons I can't figure out, at one point yesterday, I was able to relate the child FK to the parent PK, and search for content in other fields and then was able to see all the field content from the parent record in a child layout. This was how I was expecting it to work automatically, but this stopped working and I have made no progess to get it to work again. In the briefly working version, I did not ever see either the child FK or parent PK field contents - they were being set automatically, I think. Basically, I think using invisible UUIDs as key field contents makes sense over text or serially numbered keys which the user can see and not get confused, but I would rather have pure UUID keys, assigned at record creation, and just never see them. Anyone know a tutorial or webpage which explains this? Thanks in advance for any tips.
I am a new user having a problem with my first FMP DB. I think what I want to do based on what you have shown here is auto assign a UUID to the PF of my parent tables, and leave the FK in my child tables blank. Since the UUID code contains that long random string, I never want to see the contents of the Parent PK anywhere, or search using UUIDS to relate my Child FK fields.
For reasons I can't figure out, at one point yesterday, I was able to relate the child FK to the parent PK, and search for content in other fields and then was able to see all the field content from the parent record in a child layout. This was how I was expecting it to work automatically, but this stopped working and I have made no progess to get it to work again. In the briefly working version, I did not ever see either the child FK or parent PK field contents - they were being set automatically, I think.
Basically, I think using invisible UUIDs as key field contents makes sense over text or serially numbered keys which the user can see and not get confused, but I would rather have pure UUID keys, assigned at record creation, and just never see them.
Anyone know a tutorial or webpage which explains this? Thanks in advance for any tips.