Jump to content

table occurence vs direct relationship


smishler
 Share

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

Recommended Posts

I've been working with FMP for awhile now (on a relatively smiple level) but can't quite get my head around the difference or pros/cons of linking tables with direct relationships versus table occurences. Someone have a good explanation of the difference? Thanks.

Link to comment
Share on other sites

The reason that more than one table occurance exist ... or one reason is that you can not have more than one path to the same field in the same table occurance in a line of relationships else it will get all loopie. Same is for self related tables.

It can be a bit of a mind bender at first if your used to v6 logic. I still struggle sometimes.

Link to comment
Share on other sites

It's beginning to become clear now. Through the posts and a couple reference books, I see that the TOs are graphical representations (like an alias?) of the tables to help maintain order among several relationships (especially relationships involving a common field). It is considerably different than FM6. Thanks.

Link to comment
Share on other sites

Excellent, excellent resource! 3 things were key to my confusion:

1) I was trying to use the relationship graph as an ER diagram and

2) TO ≠ Table (I just couldn't get this without Harris' brilliant explanation) and

3) I had no concept of the Table Occurence Group.

Thank you.

Harris refers to common FMP nomenclature among developers. Is there a definitive site for that?

Link to comment
Share on other sites

This topic is 5794 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
 Share

×
×
  • Create New...

Important Information

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