I'd like to give you examples of both of those here because I think it's really important to understand that distinction, so that you can make sense of what you're seeing in the relationship graph. 1 Databases 2 File and Database Concepts A database is a collection of information Databases are typically stored as computer files A structured file is similar to a card file or Rolodex because it. In the meantime, I would like to draw a delineation between the concept of a base table relationship, and what I refer to as a query relationship. You must resolve the many-to-many relationship by using an intermediate table, which breaks the many-to-many relationship into two one-to-many relationships. FileMaker-Pro-10-tutorialsRelational-Database-Design-with-FileMaker-Pro8383/016 Using relationship options to create related fields. Relational databases handle one-to-one and one-to-many relationships directly. This is known at all levels within the FileMaker organization, and I'm sure in the future there will be engineering improvements to help make this a little bit easier to understand. You cannot set up a many-to-many relationship directly between two tables. Any match between the two fields is a match. And that's because the idea of relationships and the way that they're presented in FileMaker can be one of the more challenging aspects of learning FileMaker. Two fields (one in each table) with one or both containing multiple 'lines' (return-separated) that can be related ('' on the graph) and become an OR relationship. If you've watched videos on relationships or seen a class or a presentation that I've done before, you might have heard me talk about the concept of query relationships.