Database Reference
In-Depth Information
your custom menus to adapt accordingly. In fact, if you've read this topic's chapters on lay-
outs and privilege sets, you have all the tools you need to make the right menus appear to the
right people at the right time. It's a simple matter of assigning menu sets to these existing
features. You can conceal certain menus and commands from people who don't need them,
but keep them available for everybody else. Or maybe you just want menu items to show up
when they make sense for the active layout.
Once you've created menu sets by using the steps outlined earlier in this chapter, you can in-
stall them in any of several ways:
▪
By calculation
. That's what you did in the tutorial on
Editing a Menu
.
Unless you tell
FileMaker otherwise, everybody gets the same custom menus. This option works great
for a runtime file, or any situation where everyone is at the same level.
▪
On individual layouts
. In this scenario, when someone switches layouts, either by menu
command or through a script, the menu set changes to a layout-specific one of your
choosing.
Figure 13-27
shows where a menu can be attached to a layout; in Layout
mode, choose Layouts→Layout Setup to get there.
▪
By mode
. This option offers the ultimate in elegance. It lets you do things like create a
set with only one menu and just a few items, and make it the
only
menu people see when
they're in Find mode. Instead of a gaggle of buttons to perform and cancel finds, write
the appropriate scripts, and display them in the one menu, short and sweet.
▪
When a script is run
. By checking the privilege set in a script that runs when someone
logs into your file, you can load a set of menus customized to that person's level of priv-
and the Install Menu Set script step to specify which menu set installs. (If you have a re-
login script, then you need to make sure the right menu set is installed each time people
re-login.)
