Hmmm, just did a test. On my Windows XP system, using FileMaker 11, I have three tables with these relationships:
Parent::ChildID = Child::ChildID
Parent::GrandChildID = GrandChild::GrandChildID
In GrandChild, I defined these fields:
GrandChildID (uses looked up value field option to copy GrandChildID from Child::GrandChildID)
Name (uses looked up value field option to copy Name from GrandChild::Name)
When I enter a value in Parent::ChildID, the matching GrandChildID is looked up into GrandChildID from Child and the correct text from name is then looked up into Parent:Name from GrandChild::Name.
Thus, this worked for me. See any differences in your setup here?
No, I don't see anything different. This got me looking at my database a bit more and I actually have one set of lookups that are working correctly.
The work order field is used to look up a heat number field which is then used to look up the chemical percentage fields. These all work correctly.
However, my other set of related lookups, work order field to material spec field (this first lookup does work) and material spec field to a number of other rleated fields, does not work.
Any ideas on where I could begin to look to find what is different?
Just looking for distinctions here: Where this doesn't work, is it a looked up value field option or an auto-entered calculation?
What version of FileMaker are you using?
Can you confirm that the relationshps are valid? (Put a portal to the related table on your layout as a temporary check to see that the correct related records show up in it.)
Can you check the looked up value settings to confirm they are correct?
Any change in behavior if you re-index the fields on which the two relationships are based? (Turn off indexing for the field, exit Manage Database by clicking OK, return to Manage database and turn indexing back on.)
I think I remember another person posted a similar issue and it seem to have something to do with the order in which the fields were defined or the order in which the looked up values were first defined. I may not be remembering that correctly.
If all else fails, an OnObjectExit script trigger can be implemented that uses the Relookup script step to trigger the second look up.