Easy-to-follow video tutorials help you learn software, creative, and business skills.Become a member
There are a couple of different methods that you could use to create a FileMaker Pro Database, first of which would be to use one of the templates or starter solutions that we discussed in the previous movie, that are prebuilt for you. In that way, you can just go ahead and make some modifications, add some data, and you're ready to roll. But another option, which is actually a lot more popular, is to create a database from scratch, or to build all of the components from the ground up. In order to build the database from scratch, you need to first make some decisions about what type of information, or data, is going to be stored within these databases.
So the first thing that you're going to have to determine is what types of tables you're going to have in your database. So let's back up for a second. What's a Table? A Table is a container within your database that stores data. If you remember, a database is like a big bucket of information that can store all sorts of data. That's one of its key role is to store the data. But you can have different types of data within one database. So in that case, if you have multiple different types of data, each one of them needs to have its own little mini bucket within the database.
These smaller storage areas are called Tables. A database can have multiple tables, each representing a different Entity. Now an Entity, it's kind of a database term. It's useful here when we we're discussing Tables. An Entity describes a single person, place, or thing, or basically anything for which we can store data, anything that we can describe, and anything that we can store data for. So, for example, people or customers would be an Entity. That's certainly something that we could store inside of a database.
Now it's important that we remember that a database can consist of one or more tables. The database that we're going to be creating in this title, we're going to have many different tables. So a database can have many different tables, and a table can have many different records. A table can consist of records. Each record is made up of a number of fields. But focusing just on the tables, they are going to represent the groups of information that we're going to store within the database system. For example, let's say you're going to create a database that tracks the enrollment of students in classes.
You can then create separate tables that contain details about teachers, and classes, or even classrooms. They're all different types of data, but they're unique and discrete from each other. So they would deserve their own little mini storage area, or table within the database. When you have multiple tables in the database, those tables were going to have relations to each other. We'll talk about those in an upcoming chapter, but in that case, this is what we call a relational database. But a FileMaker Pro database, like any other database, is presented to the database developer as a collection of these tables that we've been discussing.
But how do we determine which tables we're going to need? A very important note here is that when you sit down at a computer and you open up FileMaker Pro to start a new database, what you're actually doing there is constructing something. Much like any other construction project that you embark on, like let's say a home construction project, your database will proceed more smoothly if you first begin with some type of a plan. The very first part of any plan, when you're developing a database, is to determine what types of information you're going to be storing inside of that database.
So the first thing that you really want to do, even before you open up FileMaker Pro, is to come up with a plan and what type of data you're going to be managing your system, and therefore, what tables you're going to need. So, for example, if it's a very complex system, then it's going to have a lot more parameters to it. You're going to have a very complex plan. But even if it's a very simple project, you still want to take a couple of minutes ahead of time, and determine what kind of data you're going to be storing. A lot of people think that they don't have a very complex solution that they're trying to build in a database, and they can skip the planning stage, but it's just as important as as it would be with something very complex.
So, first take a few minutes and look at the data. Literally sketch out what type of information you plan to manage in your database. For example, for this movie, and for the entire rest of the title, we're going to have a basic database system where we need Customers, Invoices, and Products. It's really a standard invoicing system, where Customers are ordering Products and creating invoice forms as a result. So in example like this one, we can see that we've got different types of data. So I've mentioned a couple of them already. First of all, as we're sitting down and sketching this, we realize that we're going to have to have customers stored inside of this database, so we jot that down.
We know that we're going to have Orders, or Invoices we'll call them in this case, so we jot down Invoices. And then finally we notice that we're going to have to have Products, because the Customers have got to be ordering something, so it seems to us that we can jot down Products as well in our list. So in an example like this one, we can see what types of data we're going to be storing. It's important for us to pick discrete and unique buckets of information, because after all, that's ultimately going to tell us what tables we need to define in our system. So here we see we've determined that we're going to have different groups of information in our one database: Customers, Invoices and Products.
What we've really done is created a list that tells us what tables we need to store inside of our database. Later, we'll look at how these tables are going to relate to each other, but for now, we're going to use this table list we created to start working with our new database. So by doing this exercise, we've determine that we need a Customer table, and we need an Invoice table and a Products table, because these are the discrete buckets of data that make up the database that we're trying to build.
Get unlimited access to all courses for just $25/month.Become a member
Access exercise files from a button right under the course name.
Search within course videos and transcripts, and jump right to the results.
Remove icons showing you already watched videos if you want to start over.
Make the video wide, narrow, full-screen, or pop the player out of the page into its own window.
Click on text in the transcript to jump to that spot in the video. As the video plays, the relevant spot in the transcript will be highlighted.
Your file was successfully uploaded.