

Planning is key with relational databases and for this database developers use a set of visual shortcuts to sketch out their database structures in what are called ERD diagrams (Entity Relationship Diagrams). Whether you are thinking about using FileMaker to construct a relational database or using MySQL or Oracle, the rules, theory and logic that drive how you define the relationships between your data entities and the tables will be the same. Most data requirements pretty quickly call for a relational structure rather than just a single table or “flat file” architecture. Think of five separate spreadsheets that all share common data and can be pulled together for the purpose of creating a report displaying data from all five sheets in a logical summarized printout. a database comprised of multiple connected tables. Relational Database Design 101 (part 3 of 3)įileMaker has the capacity to be used in creation of relational databases, i.e.Relational Database Design 101 (part 2 of 3).

Relational Database Design 101 (part 1 of 3): Designing a Flat File Database.The FileMaker Support Knowledge Base provides some articles on designing relational databases you may find useful: If your data has grown beyond a spreadsheet, then you should be thinking about a relational design and normalized data.
