[Forums] [Shop] [Resources] [Training] [About] [Solutions] [Consulting] [News] [Links]

Questions s I hope you enjoy this FREE online training. Let me know if you'd like to see more! You can email me at jmo@filemakerpros.com. And, if you really like this online training, consider one of my live classes based on my wildly popular book and CD ROM. Happy FileMaking!

Idiot Proofing

Using a Different Find Layout

However, this script isn't very user-friendly. The user stays in the same layout when entering data and when performing a find. The only indicator is the mode feedback area in the lower left corner of the window and the status area.

Status Area for browse and find mode

Mode Feedback Area for browse and find mode

Let's say someone didn't realize they were in find mode and started entering data? This could easily happen if the user clicked the find button, but then decided not to perform a search. Even the buttons you designed for browse mode would still work. For instance, the following script commands have dual functions:

  • New Record/Request *
  • Go to Record/Request/Page
  • Duplicate Record/Request
  • Delete Record/Request
  • Revert Record/Request
  • Exit Record/Request
* The FIND.fp5 file contains an example of this script so you can test it in browse and find mode

That means these script steps will perform a different, but similar, action in find mode. For example, the New Record script step will also create a new find request. It all depends on the current mode. In fact, a new record and a new request may appear to be exactly the same to a user who has never worked in FileMaker. On the other hand, some script steps automatically place you ind browse:

  • Sort
  • Find All *
* The FIND.fp5 file contains an example of this script so you can test it in browse and find mode

Even more confusing, some script steps perform the same action while in any mode:

  • Go to Layout *
  • Go to Field
* The FIND.fp5 file contains an example of this script so you can test it in browse and find mode

The point is that lots of problems can happen when you use the same layout for data entry and find. To prevent user confusion, simply create a specialized layout for finds.

Find w/ Find Layout script in FIND.fp5

This script now visits a special find layout to perform the find. The find layout is a little smaller than the data entry layout. One reason for the layout size change is because there are less fields on the layout. Another reason is because the change makes the user notice they are somewhere different. That's why there are a few more script steps than you might have expected. The Toggle Window script step shrinks the window down to the size of the layout.

Find layout in FIND.fp5

A few more items have been added to make the user experience as friendly as possible. First, instructions have been placed at the bottom of the layout to help guide the user. Second, a Find button has been added so the user doesn't have to click the Continue button in the status area or figure out how to type the Enter key on the keypad. The Find button has a simple script attached to a button.

Find button definition on Find layout in FIND.fp5

Previous | Next


Exclamation s Database Pros offers training classes across the globe. Classes include the wildly popular Intermediate and Advanced Scriptology training series.


Database Pros