Chapter Contents |
Previous |
Next |
The BUILD Procedure |
Note: | The menu-linking operation is performed before the procedure opens any windows. |
Tip: | By default, all MENU entries in the current catalog (the catalog that was specified in the PROC BUILD statement) are checked for selections that have the Menu-Link attribute. You can use the SELECT= option to select individual entries to check, or use the EXCLUDE= option to prevent certain entries from being checked. |
MLINK <EXCLUDE=entry-name|(entry-list)> |
<SELECT=entry-name|(entry-list)>
|
Options |
You can use the following options in the MLINK statement:
Using the MLINK Statement |
Menu links enable users to access submenu choices directly from an application's
higher-level menu. Linked menus are useful to users who have become familiar
with a system and who want to bypass intermediate menus to directly invoke
choices on secondary menus. For example, suppose a MENU entry includes a selection 3
that opens another MENU entry, and that the second MENU
entry includes a selection SALES
that displays
a sales report. If menu links are generated for the first MENU entry, then
users can go directly to the sales report by specifying SALES
in the first menu, without having to open the second menu.
Menu linking is applicable only to MENU entries. In order for a menu to be linked, the Menu-Link attribute must be assigned to it in the ATTR window of the calling MENU entry. Each time you change menus or submenus, you should re-generate the links to ensure that all linked selections are available from the highest-level menu.
Note: You can also generate menu links by issuing
the MLINK command while building the MENU entries.
Chapter Contents |
Previous |
Next |
Top of Page |
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.