Learn the differences between flat files, like spreadsheets, and relational database like FileMaker.
- [Instructor] So what makes storing data in an application like FileMaker different than just storing your data in a spreadsheet? Well, there are so many different ways that you can store data on your computer, for example in a spreadsheet or even a word processing document, but these are examples of what we call in database circles a flat file. A database, on the other hand, is a collection of data that are organized into these things that we call tables. These tables provide a systematic way of managing and updating data. A relational database is one that contains multiple tables that all relate to each other through special key fields and we'll be talking about those at length later on in this course.
Now that flat file design that we talked about before puts all the database information into a single table or list, instead of compartmentalizing it into its own tables. Now although it's nice to have all your data in one place just like you do with databases, there are some complications with storage of that data in the case of a flat file. A flat file may contain many different fields, often with duplicated data that are prone to database corruption or confusion. And if at some point you decide to merge data between two flat files, what you're going to have to actually do there is copy and paste the data between the two files.
Version control can be an issue and sharing of your data is almost impossible in many cases if you're deciding to store it in a flat file. Spreadsheets, of course, are a common example of these types of flat files. They store data in different worksheets and often these different worksheets contain similar or redundant data. A relational database, however, incorporates multiple tables with methods for those tables to work together elegantly. The relationships between the table data can be collated, merged and displayed in database layouts all representing the data stored accurately.
FileMaker Pro is an example of a relational database system that can store the data just as easily as a spreadsheet, but in the case of FileMaker, it has so many different advantages for data entry as well as how to manage database integrity that gives it a distinct advantage over its flat file counterparts. Now to better understand the advantages of a database, let's imagine the needs of two small companies that take customer orders for their products. First, let's look at company A. They use a couple of different spreadsheets, the one that you see here on screen. They've got a spreadsheet that stores all their customer information and then they have a spreadsheet where they store all their order information.
When a customer places an order with this company, a new record will have to be created, which means a new row will be created in their order spreadsheet. Because company A only has one table of data, all the information pertaining to that order must be put into a single row. So for example, we'll have to enter in the customer name along with all the data that pertains to just the order. This means that the customer's general information, in this case their first and last name, is stored in the same record as the order information.
If a customer places more than one order, their general information will need to be reentered and thus duplicated for each order that they place. So for example, the name Dennis Lambo is not only stored in the customers spreadsheet, as you see up here, but then it's duplicated as many times as Dennis Lambo places an order within the order spreadsheet. Whenever there's duplicate data like this, many inconsistencies may arise when users are trying to query the database or search for data. Additionally, if you change customer information like for example if Dennis Lambo wanted to change his first name, you'd have to go find all the iterations of Dennis Lambo in your order spreadsheet and change those manually as well.
This is what we call a data integrity issue. Conversely, if you're company B, they're much better off with a relational FileMaker database. As you see here, this is doing the same thing, storing all the customer information and all the order information. And when they create a new order, instead of having to duplicate all the information, what we do is we link to the information in another database. And since each customer has one and only one record in the database, it's easy to find them and make changes if we need to.
And the best thing about it is that you don't have to go and do any manual changes. Because all of this information is linked together through relationships, you'll see that all related data is then propagated so that you don't have to worry about things like data integrity issues. The relational database approach to entering and managing data solves problems of duplicate data and also the problems that come with changing customer information. Frankly, this is the reason that related databases were created in the first place back in the '70s. So if you're in charge of managing your company's information, you need to only change the data in one spot and then it gets propagated appropriately throughout all the different places where that data is found.
In addition, since relationships between tables and FileMaker follow the business logic of an organization using the database, it makes tasks like sharing, retrieving or even reporting on the data much easier, stable and more efficient while minimizing these data integrity errors. So the benefits of using a related database system over flat file counterparts are obvious. We're going to see various different examples of this as we go through the course, but it's important to know the advantages of having your data stored inside a FileMaker related database because your data is then going to be related within the different related tables.
Author
Released
5/9/2017- Getting going with starter solutions
- Creating relationships in FileMaker
- Defining fields
- Designing user interfaces with layouts
- Working with records
- Finding and sorting data
- Building reports
- Understanding calculations
- Automating using Scripts
- What's new in FileMaker version 16
Skill Level Beginner
Duration
Views
Related Courses
-
Learning FileMaker Go 16
with Cris Ippolite1h 16m Beginner
-
Introduction
-
Welcome1m 1s
-
Touring the Launch Center3m 54s
-
Using the exercise files1m 8s
-
-
1. Getting Started
-
What is a database?2m 23s
-
How FileMaker works6m 59s
-
Essential preferences2m 41s
-
-
2. FileMaker App Creation Essentials
-
3. Creating Tables
-
4. Creating Relationships
-
What are key fields?5m 17s
-
5. Working with Fields
-
Understanding field types7m 56s
-
Defining fields6m 48s
-
Adding fields to layouts4m 25s
-
Field options: Auto enter4m 34s
-
Field options: Validation6m 42s
-
6. Working with Container Fields
-
7. Working with Records
-
8. Importing and Exporting
-
Importing data7m 7s
-
Exporting data4m 9s
-
-
9. Creating Layouts
-
What is a layout?3m 41s
-
Working with layout themes8m 46s
-
-
10. Working with Layouts
-
Understanding layout parts6m 48s
-
Previewing the inspector1m 48s
-
Manage layouts window5m 18s
-
11. Formatting Layout Objects
-
Applying themes to layouts1m 28s
-
Applying screen stencils6m 13s
-
Gradients2m 6s
-
Layout object states6m 2s
-
Access control behavior1m 59s
-
Popovers in your layouts6m 18s
-
Setting the tab order3m 23s
-
12. Finding Data
-
New requests in find mode4m 25s
-
Search operators4m 29s
-
13. Sorting Data
-
Sorting with single criteria3m 33s
-
Sorting with related fields1m 45s
-
Sorting using custom values2m 13s
-
Sorting using buttons2m 36s
-
-
14. Value Lists
-
15. Printing and Saving
-
Printing merge letters3m 54s
-
Saving as PDF or Excel2m 23s
-
16. Reports
-
Creating subsummary reports5m 28s
-
Adding charts to reports5m 11s
-
17. Calculation Essentials
-
What are calculations?2m 46s
-
Number functions4m 29s
-
Date and time functions4m 49s
-
Text functions11m 59s
-
Get functions2m 52s
-
Logic functions10m 19s
-
-
18. Script Essentials
-
Touring the Script workspace4m 11s
-
Creating multiline scripts6m 58s
-
19. Script Triggers
-
Introducing script triggers1m 10s
-
Using object-based triggers10m 30s
-
Using layout-based triggers6m 51s
-
-
20. New Features in FileMaker 16 Platform
-
Layout objects window8m 5s
-
Card window style6m 14s
-
Support for JSON8m 38s
-
Working with JSON5m 19s
-
-
Conclusion
-
Next steps1m 14s
-
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.
CancelTake notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.
Share this video
Embed this video
Video: Comparing flat vs. relational databases