
Record navigation is done within a particular recordset; you can’t link one recordset to
another using the Dreamweaver server behaviors or Application objects.
After you’ve added your navigation controls, you may want to take the next step toward a more
complete user interface by adding Show Region server behaviors to ensure that the controls are dis-
played only when they serve a purpose. For example, if you have a navigation element that moves to
the last record of a recordset, you probably want to attach a Show If Not Last Record server behavior
to the trigger.
Using Application objects for record navigation
Although the process for setting up a single navigation control is fairly simple, you’d have to perform
that process four times (as well as attach four additional server behaviors) to accomplish what the
Recordset Navigation Bar does in one operation. The Recordset Navigation Bar is one of Dream-
weaver’s Application objects—one that can take the drudgery out of a repetitious implementation.
All the Application objects are accessible through either the Insert ➪ Application Objects menu or
the Application tab in the Insert panel.
The Recordset Navigation Bar Application object serves the following purposes:
Adds four links to the page in a borderless, single-row table: First, Previous, Next, and
■■
Last. The links may be either text or graphics.
Attaches th