The first in a series on the subject. This article presents a very simple and easy to setup method of navigation for a database, making use of repeating fields. An example file is also included so you can check it out for yourself!

You may be familiar with the Sort Records dialog in FileMaker which allows you to display records sorted by one or more fields. What you may be less familiar with is the ability to more explicitly define a sort order with the assistance of a value list. This article gives an introduction to this often overlooked feature, and provides a few examples along the way…

In this article I will demonstrate a very nice way to format a portal using conditional formatting. This method is suitable for portals whose underlying relationship is sorted by a grouping/category field - similar to if it were like a sub-summary report. The easiest way to explain it is to just get stuck in with an example, so here we go....

I've always wondered how many FileMaker dialogs you can have open at once, or more specifically, how many can you "string" together before hitting the limit, if there is one. So, though a little trial and error, I set out about trying to find the path to the most dialogs, and here is what I came up with…

The Replace Field Contents command/script step is a very powerful tool for updating field values across records in your found set. This article goes into depth about the use of this command, some of its benefits, and some of the potential pitfalls you need to be aware of…

When writing a script to carry out a particular task, ask yourself what conditions need to be true for this script to run properly.

Sometimes, a script will do something which can potentially fail, and cause a cascade effect or errors, IF the initial conditions were incorrect. It is always a good idea to check for suitable conditions before doing anything in the script…

In part two, I demonstrated how to implement the basics of the join table solution in FileMaker. While the solution works fine as an illustration for join tables, it lacked many of the basic interface features that would make it a usable solution.

In part three, I will show how to implement some of these features, namely the following: Better selection of a Student for an Enrollment, Deletion of Enrollments & Prevention of “over-enrolling” a course…

Part two carries on from where Part one left off. This article outlines the construction of a basic join table solution from woe to go…

Perhaps one of the most asked questions that I see asked on the FileMaker Cafe is in regards to join tables. While some users have an understanding of what they are, they may lack the FileMaker skills to implement them. Others are unfamiliar with the concept altogether, but will explain their real word example. Usually it is a prime candidate for a join table. This article provides a real world example that will give you an understanding of why join tables are important, and in what circumstances they should be used. The example will then be implemented in a simple FileMaker solution…

FileMaker provides us with the ability to create related records directly from a portal. This is a great and easy way to generate records without the need to script the process, and for that reason it is a popular technique among both new users and Developers alike. This article extends this concept further and suggests various user interface improvements for making data entry in this method more user friendly…