Page 437
have a toolbar. It consists of a set of iconified buttons on a form canvas. Iconified means the button has an image on it.
To create a horizontal toolbar follow these steps:
FIG. 16.34
The Canvas-view
type values picklist.
The next step is to create the iconified buttons that will appear on the toolbar. This can be done on the Object Navigator. Add the buttons to the Button Palette Block or create a new nonbase table block. In the case of the Employee Update form, a new block called "Tools" is created.
Page 438
FIG. 16.35
The form property sheet
and the Horiz. MDI
Toolbar and Vert.
MDI Toolbar
properties.
FIG. 16.36
The Employee Update
form with a blank
horizontal tool bar.
Page 439
FIG. 16.37
The Object Navigator
displaying the Tools
block and the tool
items after they have
been renamed.
FIG. 16.38
The tool item property
class.
Page 440
FIG. 16.39
The Save tool property
sheet specifying the
name of the Icon file.
The last step is to attach a When-button-pressed trigger to each of the buttons. This trigger will perform the actual function. Figure 16.40 displays the EMPCH16B.FMB form that contains a horizontal toolbar. This file is contained on the CD.
FIG. 16.40
The Employee Update
form after a horizontal
toolbar has been
added.
Page 441
The call_form command calls another form from an existing form or menu. The command overlays the child form on top of the parent form. When closing the called form, the operator returns to the original form. The new_form command calls another form, but replaces it with the called form.
The call_form command entirely overlays the existing form with the new form. If the called form is smaller that the parent form, it covers the entire form. This can be prevented by using the no_hide option. Using this option makes Forms cover only the portion of the parent form taken up by the called form.
A directory is a special application used to search the database. It consists of a two-part form. The first part consists of search fields and the second part the results of the search. This application usually has a variety of buttons that allow the operator to navigate to other applications for additional information.
A menu is a Forms module attached to a form. A menu contains a number of options that allow the operator to execute functions or call other forms. The most common use of a menu is to tie a set of related applications into a system.
Menus are usually attached to a startup application. This is the application initially launched by the operator. It sets up the system. It contains the name of the system menu, the database log in passwords, records security values, and maximizes the screen.
Toolbars are Forms objects that consist of a vertical or horizontal row of iconified buttons that execute a When-button-pressed trigger when poked.
This chapter completes Part IV of the book. At this time you should have a grasp of how to develop a Forms system. The operator adds, deletes, and modifies records on these applications. The next part of the book covers Oracle's SQL *Reports product. It is a sophisticated tool for developing and executing reports. Chapter 17 will introduce you to the Reports Runtime and Designer products. In some respects they are similar to the Forms products. The chapter will cover the Reports object navigator and data model editor. The chapter will also describe how to create a simple employee listing using the product.
The tables were loaded and the data converted in Installment 3. The portion of the Employee Project will consist of creating the system that will be used by the user to maintain the database. Create the following modules:
Department Update Form
Employee Update Form
Employee Directory
Security Administration Form