Page 282
The Tables/Columns optionThe Tables/Columns option opens the Tables/Columns dialog box. This dialog box is used to create SQL statements. Figure 12.21 shows a select command that was built using this option.
In this example, there are two dialog boxes. The top is the Tables/Columns dialog box opened when you select the option. The bottom dialog box is the PL/SQL Editor that will receive the select statement.
FIG. 12.21
The Tables/Columns
dialog box is used to
create the SQL
statement in the PL/
SQL Editor.
When the Table/Columns dialog box is first displayed, the right window, Columns, does not contain values. The left window lists the tables and views you have access to.
Selecting a table in the left window will cause it to highlight. This will populate the right window with the fields from that table, as shown in Figure 12.21. The Employee table is selected and the right window has the Employee table's fields listed.
Several of these fields have been selected. Pressing the Select-From button populates the PL/SQL Editor with the select statement. This statement holds the selected table and fields.
When the select statement contains multiple tables, the Select-From button doesn't construct the full statement because it can't highlight multiple tables. But you can construct the statement using the dialog box.
You can use the Columns button to select columns. Place your cursor in the PL/SQL Editor where you want the column. Go to the Tables/Columns dialog box, select the column you want to transfer, then press the Columns button.
The values you select are placed in the PL/SQL Editor where you put your cursor. Enter the select and from statements manually. This same procedure works for table names using the Table button.
TIP |
When selecting multiple items from a list, remember that the Ctrl and Shift keys allow you to select additional items without deselecting others. In Figure 12.21, the columns are not contiguous. The Ctrl key was held down as the items were selected. |
Page 283
The Debug Mode optionThe Debug Mode is used to place Forms Runtime in the debug mode. This invokes break processing if the Break built-in is used in any trigger. This will cause the form to stop processing at the given break points. When you initiate the Debug Mode, a check mark is placed to the left of this option.
Designer OptionsSelecting Options on the Tools menu opens the Designer Options dialog box. This dialog box consists of two tabbed sheets. The default tab is the Designer Options. The Options dialog box is shown in Figure 12.22.
FIG. 12.22
The Designer Options
dialog box.
NOTE |
You don't need to change the Save Before Generate or Generate Before Run options. Generating the form causes Designer to check PL/SQL syntax. |
When errors occur and you have trouble finding a new error, you'll be glad you haven't saved a bad version of the application. You can always use the Revert option to get a good copy of the application if you don't like to save applications that have errors.
You may want to generate the form before you run it to make sure you'll be looking at the latest version. If you don't generate the form before running it, you'll run the version of the application that was generated last. This can really confuse you if you forgot to generate the form manually.n
Page 284
The Runtime OptionsPressing the Runtime Options tab displays the Runtime Options check boxes. Figure 12.23 shows the Runtime Options tab sheet of the Options dialog box. These checkbox options control how Forms Runtime operates.
FIG. 12.23
The Runtime Options
tab sheetab.
Following are descriptions of the various Runtime options contained on the tab sheet: