Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×
The Claris Museum: The Vault of FileMaker Antiquities at Claris Engage 2025! ×

Restrictions on relationships


This topic is 6923 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

righto small...ish question...

what are some restrictions on the way to's can be related?... i.e. no unstored calc to unstored calc? ... the reason i ask is because when i try to execute a script it shows me a custom dialogue telling me that my relationships are invalid... in those relationships i have two related one text field related to another, two numbers related to one number... and one unstored calc related to another unstored calc... i assume that its the last one thats causing the problem so ill just store the results as there is no real reason for them to be unstored... but are there any other restrictions similar to this on relationships? Any advice would be appreciated...

Cheers genx

Posted

The key in the child table (right hand side) must be stored and indexed.

Calcualtions that reference global or related fields CANNOT be stored, it's not just a matter of "turning storage on" at will.

Posted

cool, thank you very much for the info, as for the unstoring ... yeh i know i forget these things sometimes

Cheers again, genx

Posted

.. speaking of which.. why do you say the child table is on the right hand side?... thats just convention right?

Posted

I love this subject, genx. Yep, it's just an old standard because in versions less than 7, the Define Relationships opened with the main (parent) table on the left and the related (child) on the right.

But with 7 & 8, the child can be on the right OR left or ABOVE (in the graph). And data can flow BOTH WAYS if structured properly (indexed keys). Data didn't flow from multiple levels deep and then on back up the chain (in prior versions). Everything is a matter of perspective. It depends upon which side of the fence you are on. When you are ON or IN a layout (table occurrence), that is always your MAIN table. As soon as you move to a related layout (table occurrence), *IT* becomes your main table. :wink2:

Your Main table (the one you are standing in) can have unstored and globals as the key fields. Any related table occurrences other than the main MUST have keys that can be indexed or the data can not flow from that related to the main.

This topic is 6923 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.