Database Reference
In-Depth Information
must enter text in the Default Button box, but you can leave the other two blank. Buttons you leave
blank won't appear in the dialog box. In this case, the standard text of OK makes most sense—it's
not common to change this text when you're giving users a message and don't want a response. By
default, the Commit Data option is selected for each button. But when you're just giving the user
information, you should turn this option off. Learn more on page 674. Bottom: The dialog box that
results from the settings shown above. This, the simplest version of a custom dialog box, has a title,
a message, and a single button—just the basics for getting a message to folks using your database.
The title appears along the top of the dialog box, the message in the middle, and the button at the
bottom.
Asking a Simple Question
Up one level of complexity, you can create a dialog box that asks a simple question and gives
users a choice of responses. Then your script can take action based on that response. This
process is very similar to the warning users get if they delete a record: FileMaker asks if the
user if he wants to delete the record and gives him the option to cancel the delete action.
Users are very familiar with this process, so if you have a script that posts a customer pay-
ment, you could show a custom dialog box to ask, “Are you sure you want to post a pay-
ment?” and you'd include Post Payment and Cancel buttons for feedback (
Figure 17-4
).
