1 Reply Latest reply on Dec 8, 2012 7:12 AM by philmodjunk

    Table Occurrence Concepts



      Table Occurrence Concepts



           I am looking for feedback on my understanding of Table Occurrences.  Do I get it?


           Being new to Filemaker Pro (v11) but well versed with Microsoft Access, I constantly find myself trying to relate (no pun intended) my knowledge of Access to the language used by FMP in describing its functionality.  An example of this is with trying to understand the concept of Table Occurrences.


           In Access, one has Tables, Queries, Forms, Reports, and Macros.  Within Queries, each query can have multiple tables in a relationship.  And each query's table relationship is unique to that query.  The same table can be used by mulitple queries.  For example, if I relate Contacts to Events in one query, I can have another query where Events are related to Locations.  The Events data is the same in the two queries but they are related separately to Contacts and Locations via the separate queries.  I am thinking that the same table, referenced multiple times across different queries is the same concept as FMP's Table Occurrences.


           Also in Access, each query's table relationship is stored a as separate entity with the query.  In FMP, there is one view that shows all relationships.  


           Does it seem like I am understanding FMP's Table Occurrence concept? 


           BTW, I have found the following resources to be invaluable in my ramp up the learning curve.






        • 1. Re: Table Occurrence Concepts

               Glad my posts were of help to you. wink

               That seems a pretty good analysis of the differences. And just when you get if figured out, FileMaker 12 gives you ExecuteSQL() and a (limited) ability to go back to using SQL queries to define relationships "one the fly" in order to query data from your FileMaker Pro database.

               When you set up a layout and select a table occurrence from the "Show Records From" drop down, it's roughly similar to setting up that underlying SQL query that you use in Access--drawing the "join" info from the global relationships graph, but without the "where" clause to specify what records are accessible--that being managed on a dynamic basis via manual or scripted "Finds" performed from the context of the layout's table occurrence.