That’s a way of saying “this order belongs to that customer.” Another way to think about this is that relationships are a pre-specified query from one table occurrence to the next. For example, you might link a customer ID on an Order record with a customer ID on a Customer record. This is done by linking one or more fields in one table occurrence to one or more fields in another table. Finally, what is a relationship? A relationship is way of reaching data in one table based on the information that resides in the records of another table. The use of these table occurrences will be easier to understand once w look at relationships. Layouts, for example, are based on a specific table occurrence and can access the data in the specific table occurrence or any data related to that table occurrence. This window or viewpoint can be used to see and/or manipulate the data that resides in the table. The best way to think of a table occurrence is as a window or point of view into the actual table. All database data in FileMaker is stored in tables.Ī table occurrence is a visual representation of a given table in the Relationships Graph. In FileMaker, tables are created in the Manage Database Dialog under the Tables tab. A table is thus the collection of these records and their field data. These columns are often called “fields” in database parlance.
The columns define the common data elements stored for each instance of a thing: a car’s weight and model year, or a scholarship’s amount. These rows are often known as “records” in database terminology. Each row represents one instance of a thing: one vehicle, or one car, or one scholarship. A table stores its data in a row-and-column format. A table stores information about one specific kind of thing: for example, a given table may store information about vehicles, or swimmers, or scholarships. The best place to start is to first understand a table. To understand how tables, table occurrences, and relationships work together we must understand each one. However, once you do understand the difference it may help you to utilize relationships in FileMaker in ways you did not realize were possible. If the Relationships Graph for your FileMaker solution never has more than one table occurrence per table, then it may not be important to understand the differences. Understanding the difference between a table and a table occurrence is vital when developing a relationship in a FileMaker solution.
0 kommentar(er)
