you'll learn to add dynamic images, repeating regions, pagination functionality, and more. This is just the tip of the iceberg. Dynamic Images Now that you've created dynamic text within your application, you're ready to begin adding dynamic images. The images we'll add here are not the typical static images you have used throughout the book; instead, they will be dynamic. Remember, we added the path to the image of each item in the EmployeeStore table. What we want to now do is dynamically show the image, based on the path provided within the ImageURL field, on our dynamic EmployeeStore web page. To do this, follow these steps: 1. Place your cursor in the leftmost cell (we'll use this cell to place the product's image dynamically) and vertically align the cursor to the top of the cell by choosing the Top option from the Vert menu in the Properties Inspector. 2. Select Insert, Image. The Select Image Source dialog appears. 3. Near the top of the Select Image Source dialog are options for selecting the image from the File System (static) or from Data Sources (dynamic). Select the Data Sources option. The Select Image Source dialog's interface changes to allow you to select an image path from the recordset. Select the ImageURL field. 4. Click OK. The dynamic image placeholder appears within the cell. Save your work and test the results in the browser by pressing the F12 key. The image for the Dorknozzle T-Shirt should now appear as shown in Figure 25.33. Figure 25.33. The image is dynamically placed based on the path within the database. [View full size image]   Recordset Paging Now that you've seen how easy it is to place dynamic content on a page, you'll probably want to begin adding features that allow your users to interact with the content on your pages. Paging, for example, enables your users to page through items in the recordset until they find the item they are looking for. For every press of a button, your users can advance to the next record or, conversely, return to a previous record. Developers gain certain benefits from pagination, including: Load time: Rather than the page having to process multiple records at once, it processes only a predefined set of records at a time. Records are loaded only as users advance forward to another record. Size constraints: By paging through a recordset, screen real estate is gained. The records are loaded in a certain area of the page rather than all records showing continuously down the page. Dreamweaver's pagination behaviors are located in the Add (+) menu in the Server Behaviors panel and include the following behaviors: Move to First Record: Returns the user to the first set of records in the recordset. Move to Previous Record: Returns the user back one set of records. Move to Next Record: Advances the user one set of records forward. Move to Last Record: Advances the user to the last set of records in the Recordset. Move to Specific Record (ASP only): Advances or returns the user to a set of records specified by the developer or by a parameter passed by the user. NOTE In ColdFusion, the pagination behaviors are named a bit differently. For example, ColdFusion uses Move to First Page, Move to Previous Page, Move to Next Page, and Move to Last Page.