Getting Started

It's time to roll up your sleeves and actually put FileMaker Pro to use. Most of this book deals with being a FileMaker Pro developer ”someone who is focused on the programming side of creating and managing FileMaker Pro solutions. However, ironically, development comprises only a small percentage of the overall time a given database gets used. Much of the time a FileMaker solution will simply "be in use," and its users will care nothing for scripting, calculations, or the vagaries of user -interface design. They will simply be involved with working with your creation and will not need to know anything of the development side of FileMaker Pro.

Becoming facile in working with FileMaker Pro databases will prove quite helpful in allowing you to quickly access the information you want and to understand the underpinnings of any database, regardless of user interface.

This chapter introduces you to how to make the most of FileMaker databases that have already been built. All FileMaker databases ”often called solutions, systems , or applications ”have certain common elements, and becoming adept in developing FileMaker Pro solutions will not only help you manipulate and analyze data better, but will assist you in extending what you can accomplish with that data. We'll cover some broad concepts at first, move into the nuts and bolts of working with databases, and finally wrap things up with some techniques to help you become a FileMaker Pro power user.

One quick note before we begin: This chapter assumes you bought this rather hefty tome for a reason (unless of course you're one of the authors' mothers), namely that you want to learn as much as you can about FileMaker Pro. Although the concepts and functions described in this chapter can be fairly basic (how to open a database, for example), it also covers a fair number of advanced topics as well. This chapter is a good place to start if you're unfamiliar with FileMaker Pro, or if you still don't quite feel comfortable using a FileMaker Pro database.

Before going much further, we need to be clear on some basic FileMaker Pro vocabulary. Databases store collections of information, and one of their primary functions is to properly identify the information they store. It's not enough to simply save the text strings "Pink Floyd" and "Dark Side of the Moon" in a file. For a database to be useful, you need to know that Pink Floyd is a band and that the Dark Side of the Moon is an album (one of the greatest of all time!).

For a database to fulfill its primary function, a developer needs to have properly identified all the appropriate elements of information you or your organization wishes to store and use. It is in these identifications that information becomes meaningful.

Records and Fields

Databases store information about one or more different kinds of "items." For example, a database might store information about music albums, or musicians , or guitar manufacturers. In FileMaker, each individual item is referred to as a record . So in a database of music CDs, each record represents an individual CD.

To track the attributes of items or specific information ”for example, Dark Side of the Moon 's release date of March 24, 1973 ” fields are defined, specific to each type of item. These fields hold and also identify the type of information found for each record. Examples of fields that might be found in the music CD database are release date, recording studio, and so on.

In FileMaker Pro you will be working with a specific individual record at a time and will be viewing (and storing) information from that record's fields.

NOTE

For those of you familiar with SQL, a row corresponds to a record in FileMaker Pro, and a column corresponds to a field .

For more information on SQL and how it relates to FileMaker Pro, see "Importing from an ODBC Data Source," p. 552 .

Tables

It's important to have a grasp of what a table is when working with FileMaker Pro.

Simply stated, a table is a collection of like records. You might have a table of automobile model records and another table of manufacturer records. Miata would belong in the automobile table, and Mazda in the manufacturer table. From the music example, music albums would belong to a table, musicians to another, and genres to another. An album isn't a genre , and nor are musicians the same as the albums they create.

For the purposes of using FileMaker Pro, you really need to remember one thing: every layout (a view or form for data) in FileMaker Pro is associated with a specific table. If you look at a layout with a picture of a Mazda Miata, and fields that break out the attributes of that car, more than likely you're in an automobiles table. If you see a layout with "Mazda" at the top and multiple car models listed, you're more than likely in the manufacturer table. This will come into play later in the chapter when you begin working with multiple records and found sets.

To explore working with multiple record sets, see "Working with a Found Set," p. 47 , later in this chapter.

NOTE

In FileMaker Pro, you can have as many tables in a single file ( .fp7 document) as you need, and FileMaker Pro 7 is a fully relational database platform. Versions of FileMaker since version 3's introduction in 1995 were also fully relational, but prior versions allowed only one table per file.

Database solutions would often be collections of files and require that you open all these multiple files at once to use a solution. Now in FileMaker 7, you can consolidate solutions into single files with multiple tables.

To dig deeper into working with multiple tables and understanding relational data models, see Chapter 6, "Working with Multiple Tables," p. 153 , and "Understanding Relationships," p. 130 .

FileMaker Pro Navigation

One of the first things you'll want to do when you open a database in FileMaker Pro is navigate the various screens, called layouts , that the developer designed as the interface for the database. Using these layouts, you can view records, enter data into fields, see reports , run scripts, and more.

There are two important work areas to distinguish from one another in a FileMaker Pro database: the Status Area on the left and the Layout area on the right (see Figure 2.1).

Figure 2.1. These are the primary areas of all FileMaker Pro databases; in some cases, however, a developer might have hidden the Status Area.

Layouts

Most FileMaker Pro databases open to a data entry layout. Generally you have access to fields, commonly designated by a field border or embossing of some kind (again depending on the design or dementia of the database's developer), or you may come across a layout used for reporting purposes only. Figures 2.2, 2.3, and 2.4 illustrate just a few examples of layouts that you might find with databases created in FileMaker Pro.

Figure 2.2. FileMaker's built-in templates offer a simple, clean interface. Shown here are a form layout (one record per screen) and a list layout (multiple records per screen).

Figure 2.3. FileMaker Applications ”commercially available database solutions from FileMaker, Inc. ” demonstrate the possibilities of more feature-rich systems. (Screenshots provided by permission of FileMaker, Inc.)

Figure 2.4. Here's a departure from the staid designs of typical productivity applications!

The Status Area

The Status Area serves as a primary control center for FileMaker Pro. In Browse mode ”the state in which all data entry and general use occurs ”the Status Area displays a book icon and other elements for navigating a database solution.

FileMaker Pro has four modes, which we'll explain later in this chapter. For now, note that the Status Area changes depending on which mode you're using. In Find mode it allows access to search functions and special search wildcard characters . In Layout mode the Status Area contains most of the tools used for controlling the look and feel of your database.

Figure 2.5 details the various elements of the Status Area, as it appears in Browse mode.

Figure 2.5. Note the various functions of the Status Area in Browse mode. To jump to a specific record, type a number into the record number field and press Enter.

The elements of the Status Area include:

• Layout Pop-up Menu ” Enables you to navigate from layout to layout in your database.

• Book Icon ” The book icon enables you to page through each record in your database. You stay on the same layout, but you see the information for each record in your database as you click through your records. The slider below enables you to jump ahead and back by multiple records.

• Current Record Number ” Not to be confused with a record identifier, key, or ID, this number indicates which record in your current set you're viewing. FileMaker Pro allows you to establish found s ets ”groups of records with which you're currently working ”and this number shows where your current record lies relative to the found set.

• Found and Total Records ” These numbers show how many records are in your found set compared to the total in your entire database. Found sets are covered in more detail later in the chapter.

• Sort Status ” FileMaker Pro allows you to order your records based on some criterion. Depending on how your found set has been sorted, the Status Area shows "sorted," "semi-sorted," or "unsorted." A semi-sorted state would occur if you were to sort the records in your database and then created a new record.

• Zoom Icons ” These allow you to zoom in and out on a given layout.

• Status Area Toggle ” Allows you to show and hide the Status Area.

• Mode Menu ” This pop-up menu functions in the same way as the mode icons.

CAUTION

You'll notice something missing from FileMaker Pro: back and forward buttons . It's important that you not confuse the book icon with such. The book icon enables you to page back and forward through your data as opposed to paging through your layouts in Browse mode.

Some users familiar with the Web might expect the book icon to step forward and back through their navigation history within a database.

FileMaker Pro Modes

You'll interact with your FileMaker Pro databases via one of four modes. At times, developers choose to tailor a layout for use with a specific mode, but more often than not layouts can be effectively used with all four.

To familiarize you with the four modes, here's a simple description of each. To switch between modes, use the V iew menu.

• Browse Mode ” Browse mode is FileMaker Pro's "primary" mode, where all data entry occurs, and generally the one that you'll primarily interact with in a given solution.

• Find Mode ” Here one creates and then performs find requests to search for specific sets of records or information in a given solution.

• Preview Mode ” When preparing to print from FileMaker Pro, you may opt to switch to Preview mode to see what a given layout will look like after it is printed. Developers may also build Preview mode steps into their reporting functions so that you can review a document before sending it to a printer.

• Layout Mode ” It is in Layout mode that most development occurs. Here developers can manipulate all the elements of a given layout, including controlling all the things that appear on that layout.

NOTE

You can change modes in three other ways: Use the menu at the lower left of your screen, use the mode tabs at the top of the Status Area, or a developer may program a number of different functions and/or buttons that switch modes.

Views

In addition to the modes of FileMaker Pro, there are three views as well. To change between them, use the V iew menu as well.

• Form view ” Allows you to see and manipulate only one record at a time (see Figure 2.6).

  Figure 2.6. Form view is usually where most data entry is performed.

  
  

• List view ” Here you can display multiple records. At any given moment, you still are working with only one specific record while still being able to view the rest (see Figure 2.7).

  Figure 2.7. List views can also include summary data.

  
  

• Table view ” Table view simply displays the raw data for a given record (depending on what fields have been placed on a layout). It looks quite similar to a spreadsheet application (see Figure 2.8). This is extremely handy for reviewing large groups of data quickly without pesky user interface elements getting in the way. A developer has little control over how a Table view appears.

  Figure 2.8. In Table view you can automatically resize, move, and sort with column headers.

  
  

Buttons

Notice we've largely been talking about fields on layouts. Most FileMaker Pro solutions also include buttons. Figure 2.9 shows a few examples.

Figure 2.9. Buttons can come in all shapes and sizes in FileMaker Pro. Text can be a button, a field can be a button, and even just a mysterious blank area in the middle of a layout can be a button.

Buttons trigger actions ”often by launching scripts that developers write ”and are specific to a given FileMaker Pro database. Buttons can perform dozens of actions, such as creating a new record, deleting a record, navigating to another layout, performing a calculation, performing a find request, controlling windows , even spell-checking and emitting a simple "beep." The possibilities are nearly endless.

You'll need to become familiar with the specifics of a given FileMaker Pro solution to come to understand what its buttons do. The person who built the system should have those details, or should have provided some form of training or documentation.