From the course: Learning FileMaker 16

Unlock the full course today

Join today to access over 22,400 courses taught by industry experts or purchase this course individually.

Deciding what fields you will need

Deciding what fields you will need - FileMaker Pro Tutorial

From the course: Learning FileMaker 16

Start my 1-month free trial

Deciding what fields you will need

- [Instructor] Like many other databases, a FileMaker Pro app is presented to the developer as a collection of tables, each containing a number of fields. And if you've worked in other database environments, you might be accustomed to the term columns instead of fields. Either term is meaningful and acceptable but in FileMaker Pro user interfaces, we use the term field which I'll be referring to moving forward. Now, a FileMaker database can be made up of either one table or many different tables. Each of those tables can have an unlimited amount of fields defined in them, although I would be cautious about defining too many of them because if you have a ton of different fields, you might be asking yourself whether or not that you might need another table. For example, if you find yourself defining fields like address one, address two, address three, address four, address five, what you might actually have determined is that you're trying to create a child table inside of a parent…

Contents