List of Figures

Chapter 1: An Introduction to the Data-Driven World

Figure 1.1: Processing data via the Internet

Chapter 2: An Introduction to Dreamweaver MX

Figure 2.1: Choose your default editor for various file types from the Default Editor screen.
Figure 2.2: Dreamweaver MX shows you the file types for which it will become the default editor after installation.
Figure 2.3: The first time you run Dreamweaver MX, you choose the style of interface you want to use.
Figure 2.4: You can also choose a coding window as a default interface in Dreamweaver MX.
Figure 2.5: You can use the Preferences window to configure Dream- weaver MX to your liking.
Figure 2.6: You can transform Dreamweaver MX's simple text descriptions to eye-catching icons by choosing this option.
Figure 2.7: The Icon option also displays a toolbar, called the Launcher, at the bottom of your document window.
Figure 2.8: Choose your Launcher options from the Panels category of the Preferences window.
Figure 2.9: Use the AddBrowser dialog box to add a browser.
Figure 2.10: Dreamweaver MX can check your work to ensure it adheres to a certain language syntax.
Figure 2.11: You can validate your work in several ways in Dreamweaver MX.
Figure 2.12: Dreamweaver MX lets you control how it will try to fix what it deems as erroneous HTML.
Figure 2.13: Dreamweaver MX will warn you when it changes your code.
Figure 2.14: The databases tab shows you the status of steps you must take to fully utilize Dreamweaver MX's database features.
Figure 2.15: Dreamweaver MX lets you create many types of documents, from ASP pages to Framesets to complete designs.
Figure 2.16: Since we're creating a new site, we need to define a few of the site's properties in order to use dynamic data.
Figure 2.17: You use the Site Definition window to set up a Dream- weaver MX site.
Figure 2.18: Defining your testing server is crucial to Dream- weaver MX development.
Figure 2.19: You use the Basic tab to specify the minimum requirements for your site.
Figure 2.20: The Basic tab guides you through a questionnaire to set up your site.
Figure 2.21: Your definition options depend on the type of testing server connection you elect.
Figure 2.22: You specify a common network path when you choose Local/ Network as your connection type.
Figure 2.23: After you specify the URL to use for your testing server, you can save debugging time by immediately testing whether Dreamweaver MX can connect to it properly.
Figure 2.24: You need to decide whether you want to use Dreamweaver MX's check-in/ check-out procedure.
Figure 2.25: The Summary screen shows you a summary of the options you've chosen for your site.
Figure 2.26: Options for creating a database connection from an ASP page
Figure 2.27: After you establish a data connection, Dreamweaver MX gives you access to all the database components such as tables, views, and stored procedures.
Figure 2.28: The Site tab can be used to alleviate many of the headaches associated with maintaining your website's structure and files.
Figure 2.29: The Local View of our new site shows there are no files yet in the site.
Figure 2.30: To import the existing site, switch to the proper view and click the Get Files button. You'll be asked for confirmation.
Figure 2.31: Our import of an existing site is a success!
Figure 2.32: The site map in action
Figure 2.33: Dreamweaver MX checks our site for links it thinks might be broken.
Figure 2.34: Dreamweaver MX can automatically update links to moved web pages for you.

Chapter 3: Coding Practices for Dreamweaver Development

Figure 3.1: Another strength of Dreamweaver MX is its ability to guide you in making your websites compliant with the W3C Web Accessibility Initiative.
Figure 3.2: Dreamweaver MX asks for Accessibility components when you drop a text field onto a form.
Figure 3.3: A site map will help you keep your code's goal in perspective during development.
Figure 3.4: Dreamweaver MX behaviors save you time and effort by automatically creating useful scripts for you.
Figure 3.5: You can validate a field as a number, as a numeric range, or as an e-mail address.
Figure 3.6: Launch the Tag Library Editor from the Edit tab.
Figure 3.7: The Tag Library Editor will also show you a preview of how your tag will appear in your code.
Figure 3.8: We've changed the standard formatting of our HTML <body> tag.

Chapter 4: An Introduction to HTML Forms

Figure 4.1: Our simple form displays a Submit button.
Figure 4.2: Clicking the button displays the button's value.
Figure 4.3: Name and describe the DSN.
Figure 4.4: Windows adds the new ODBC DSN.
Figure 4.5: Enter a customer name.
Figure 4.6: The page returns orders for the matching customer.
Figure 4.7: The results of combining our two previous scripts
Figure 4.8: The <select> element displays a fixed list.
Figure 4.9: Use the <select> element to display a drop-down list.
Figure 4.10: Choose a form object from the Insert menu, or display the Forms panel to access form objects.
Figure 4.11: Forms are easily identified by the red dotted outline around them.
Figure 4.12: Open the Properties panel to modify a form object's properties.
Figure 4.13: Using the Get method displays field names and values in the URL.

Chapter 5: Designing the Database

Figure 5.1: The publisher primary key becomes the foreign key in the books table.
Figure 5.2: Create a linking table to relate two many tables.
Figure 5.3: An inner join is well represented by two intersecting circles.
Figure 5.4: An inner join returns records only when there's a matching key value.
Figure 5.5: The shaded area represents the records returned by a left outer join.
Figure 5.6: A left outer join returns all records from the one table.
Figure 5.7: The right outer join returns all the records from the many table and only those records that match a key value from the one table.
Figure 5.8: Use a right outer join to return all the publishers and any of their listed books.
Figure 5.9: Join lines graphically define the relationships between our tables.

Chapter 8: SQL Server and the Web

Figure 8.1: Call a view in a SELECT statement to see its results.
Figure 8.2: Enter the stored procedure in the Query Analyzer.
Figure 8.3: Call the stored procedure.
Figure 8.4: You can pass a parameter to a UDF.
Figure 8.5: This UDF returns orders for a specific customer.
Figure 8.6: Return all the orders for a specific employee.

Chapter 9: Microsoft Access and the Web

Figure 9.1: The Asc function returns only the resulting value.
Figure 9.2: Query Design view reveals a lot about a query.
Figure 9.3: View referential integrity settings in the Edit Relationships dialog box.
Figure 9.4: The SupplierID control uses a Jet SQL statement.
Figure 9.5: The Jet SQL statement populates the control with a unique list of suppliers.

Chapter 10: Connections and Scripting

Figure 10.1: The ODBC Data Source Administrator dialog box
Figure 10.2: The Create New Data Source dialog box
Figure 10.3: The ODBC Microsoft Access Setup dialog box
Figure 10.4: The ODBC Data Source Administrator dialog box
Figure 10.5: The Data Source Name (DSN) dialog box
Figure 10.6: The Data Source Name (DSN) dialog box
Figure 10.7: The Select ODBC DSN dialog box
Figure 10.8: Define a Dream- weaver MX data connection name
Figure 10.9: The Custom Connection String dialog box
Figure 10.10: OLE DB Connection in the Custom Connection String dialog box
Figure 10.11: The OLE DB Connection dialog box
Figure 10.12: The Provider tab of the Data-Link Properties dialog box
Figure 10.13: The Connection tab of the Data-Link Properties dialog box
Figure 10.14: The Connection String Template dialog box
Figure 10.15: The Microsoft Access 2000 connection template loaded in the Connection String text field
Figure 10.16: The SQL Server Connection dialog
Figure 10.17: The Sun JDBC_ODBC Driver (ODBC Database) dialog box
Figure 10.18: The INET Driver (SQL Server) dialog box
Figure 10.19: The Custom JDBC Connection dialog box
Figure 10.20: The Data Sources section in the ColdFusion Administrator
Figure 10.21: The Databases tab in Dreamweaver MX displaying data sources from the ColdFusion Administrator
Figure 10.22: The MySQL Connection dialog box
Figure 10.23: The web server must have access to your database file
Figure 10.24: The Security tab in the SQL Server Properties (Configure) dialog box

Chapter 11: ColdFusion and Dreamweaver MX

Figure 11.1: You use the ColdFusion Administrator to control how the ColdFusion Server behaves.
Figure 11.2: A 404, or Page Not Found, error is not an elegant way to handle a missing page error.
Figure 11.3: ColdFusion let's you specify a custom page that should be shown to the user when it can't find the page that was requested.
Figure 11.4: You should immediately set client variables to a data source instead of using the default of the system Registry.
Figure 11.5: You control how long ColdFusion Server stores memory variables through the Memory Variables setting.
Figure 11.6: The Settings Summary gives you a report that details every value for every setting in your ColdFusion Server.
Figure 11.7: The Data Sources window lets you manage the data source connections used in your ColdFusion applications.
Figure 11.8: The Debugging Settings category will become one of your favorite ColdFusion Administrator areas.
Figure 11.9: The debugging information you see may look similar to this.
Figure 11.10: You can display the debugging information in its own window.
Figure 11.11: Or you can dock the debugging information within a pane of the current page.
Figure 11.12: To actually see the debugging information, you either enter a list of IP addresses or remove all the IP addresses.
Figure 11.13: The simple output from our script displays the contents of the variable cMyName.
Figure 11.14: The <cfoutput> and the <cfquery> tags work in conjunction to display a list of records.
Figure 11.15: The CFML Basic tab gives you quick access to some of the commonly used ColdFusion tags.
Figure 11.16: Entering server variables into your code is a snap.
Figure 11.17: Specify your choices for the <cfquery> tag by concentrating on the data and not the syntax of the tag.
Figure 11.18: You can instantly turn a chunk of code into a comment by selecting it and clicking the Comment button.
Figure 11.19: The CFML Flow tab gives you access to flow-control constructs.
Figure 11.20: Lock your application and session variable updates to ensure that their integrity remains intact.
Figure 11.21: CFLoop is a powerful command that creates looping structures using any of five different types as the key.
Figure 11.22: The CFML Advanced tab gives you access to some of the real power behind ColdFusion.
Figure 11.23: ColdFusion has its own method for setting a cookie, and Dreamweaver MX aids you in setting the cookie.
Figure 11.24: You can quickly set your <cfapplication> tag code by clicking the CFApplication button on the Insert bar.

Chapter 12: JavaServer Pages

Figure 12.1: Viewing the output from helloWorld .jsp in Internet Explorer
Figure 12.2: Viewing the output from scriptlet.jsp in Internet Explorer
Figure 12.3: Viewing the output from declaration.jsp in Internet Explorer
Figure 12.4: Viewing the output from taglib.jsp in Internet Explorer
Figure 12.5: Viewing the output from cookiewrite jsp in Internet Explorer
Figure 12.6: The result of redirecting to the helloworld jsp page
Figure 12.7: Viewing helloWorld_ form.htm in Internet Explorer
Figure 12.8: Viewing the output from helloWorld_ action.jsp in Internet Explorer
Figure 12.9: Viewing helloWorld_ form2.htm in Internet Explorer
Figure 12.10: Viewing the output from helloWorld_ action2.jsp in Internet Explorer
Figure 12.11: Viewing the results of cookieread jsp in a browser
Figure 12.12: The Dreamweaver MX Sun JDBCODBC Driver (ODBC Database) dialog box
Figure 12.13: The JavaBean Collection dialog box
Figure 12.14: The Bindings panel
Figure 12.15: The Dreamweaver MX UseBean dialog box
Figure 12.16: The Dreamweaver MX SetProperty dialog box
Figure 12.17: The Dreamweaver MX GetProperty dialog box

Chapter 13: Active Server Pages

Figure 13.1: Viewing the output from response- Write.asp in Internet Explorer
Figure 13.2: Viewing the output from response- Flush.asp in Internet Explorer
Figure 13.3: Viewing the output from response- End.asp in Internet Explorer
Figure 13.4: Viewing Hello- World1_form.htm in Internet Explorer
Figure 13.5: The results of HelloWorld1_ action.asp displayed in Internet Explorer
Figure 13.6: Viewing Hello- World2_form.htm in Internet Explorer
Figure 13.7: The results of HelloWorld2_Action.asp displayed in Internet Explorer
Figure 13.8: The ASP tab in Dreamweaver MX

Chapter 14: Dreamweaver and ASP.NET

Figure 14.1: Viewing the output from helloWorld- CSharp.aspx in Internet Explorer
Figure 14.2: An event-driven Web Form
Figure 14.3: Dreamweaver MX inserts the Textbox server control
Figure 14.4: Viewing the output from helloWorldauto- post-VB.aspx in Internet Explorer
Figure 14.5: Dreamweaver MX Tag Chooser for ASP.NET
Figure 14.6: The Dreamweaver MX TagEditor for ASP.NET
Figure 14.7: Viewing the hello-WorldValidate-VB.aspx form in Internet Explorer
Figure 14.8: Clicking the Enter button without a value in the text box displays the helloWorld-Validate-VB.aspx error message.
Figure 14.9: Viewing the output from ResponseWrite.aspx in Internet Explorer
Figure 14.10: Viewing IsPost-Back.aspx in Internet Explorer
Figure 14.11: Viewing IsPost-Back.aspx in Internet Explorer
Figure 14.12: The HelloWorld_WS.asmx class description page

Chapter 15: ADO.NET

Figure 15.1: The hierarchy of objects in a DataSet
Figure 15.2: The Deploy Supporting Files To Testing Server dialog box in Dreamweaver MX
Figure 15.3: Creating a DataSet
Figure 15.4: The DataSet shown in the Bindings panel
Figure 15.5: Dynamic Text result
Figure 15.6: The Tag Editor for a DropDownList. (top) The General category; (bottom) the Data category.
Figure 15.7: Data bound DropDownList browser result
Figure 15.8: The Repeat Region dialog box
Figure 15.9: The Repeater server control
Figure 15.10: The DataList dialog box
Figure 15.11: Add DataField variables to the DataList Template Contents Area
Figure 15.12: Inserting template code in the DataList dialog box
Figure 15.13: The DataList in Design mode
Figure 15.14: : DataList.aspx
Figure 15.15: The DataGrid dialog box
Figure 15.16: DataGrid_ simple.aspx

Chapter 16: PHP and Dreamweaver MX

Figure 16.1: PHP has become a popular web-scripting language since its release, and it continues to grow in popularity.
Figure 16.2: Single quotes tell PHP to take everything literally.
Figure 16.3: PHP continues code processing when it encounters an undefined variable, but displays a notice.
Figure 16.4: This is the same code with the php.ini error_reporting option set not to show notices.
Figure 16.5: Both echo and print do basically the same thing.
Figure 16.6: This simple form uses the Get method.
Figure 16.7: The HTTP Get method passes form variables in the URL query string.
Figure 16.8: Post doesn't send the query string, so we use $http_post_vars to retrieve the variable.
Figure 16.9: Dreamweaver MX's PHP tab
Figure 16.10: Create a new PHP Dynamic Page.
Figure 16.11: e're building a connection to our MySQL table.
Figure 16.12: Our connection was successful.
Figure 16.13: We're going to select the data, sorted by last name, from the tblauthors table.
Figure 16.14: We can test to make sure our query works before we leave the query configuration.
Figure 16.15: Dreamweaver MX guides us through creating our dynamic table.
Figure 16.16: We now have a repeating region within our table.
Figure 16.17: We created our dynamic PHP/MySQL data page with just a few clicks and a little information.

Chapter 17: Database and System Security for the Internet

Figure 17.1: Windows ships with a backup software solution, but you might want to invest in something hardier.
Figure 17.2: A mapped drive to the live server can be dangerous unless you're very alert
Figure 17.3: Microsoft has made it quick and easy to get patches through Internet Explorer.
Figure 17.4: Windows Update will scan your system and report the patches that are available for your system.
Figure 17.5: You can find Sun's offering of patches for Linux at their patches site
Figure 17.6: Apple also has downloadable updates for its easy-to-use operating system.
Figure 17.7: Viral infection can come from many sources.
Figure 17.8: A typical firewall placement
Figure 17.9: Gibson Research Center offers a quick-check security tool that will give you an idea of how secure your computer is.
Figure 17.10: Many people new to web development make the mistake of putting their database in the same folder as their web files.
Figure 17.11: Your database should at least be in its own secure directory or folder, if not its own server.
Figure 17.12: Although this form isn't pretty, it contains the required elements for a login page.
Figure 17.13: Dreamweaver MX lets you quickly build a login form.
Figure 17.14: Choose the proper login options in the Log In User dialog box, and Dreamweaver MX will do the rest.
Figure 17.15: You can test for whether the user is logged in or whether the user meets specified level criteria.
Figure 17.16: Our login failed, so we see our No Access page.
Figure 17.17: Dreamweaver MX will automatically create a log out script for you.
Figure 17.18: Our log out screen will remove our session variables and take us back to the login screen.
Figure 17.19: This time, we're going to use security levels in our login process.
Figure 17.20: You specify the levels to which you want to give access to this page.
Figure 17.21: We've just given Admin-level users access to this page.
Figure 17.22: Registration starts with an insert form.
Figure 17.23: We use an Insert Record Server Behavior as the first step in our registration page.
Figure 17.24: Specify your user- name field and the page the user should see if the username exists.
Figure 17.25: Our Username Exists notice page is rather simple, but includes a javascript : history link.
Figure 17.26: We're entering a "new" user's information.
Figure 17.27: Dreamweaver MX found our username to be duplicated, so it's sending us to our notification page.

Chapter 18: Structured Query Language

Figure 18.1: Use SELECT to retrieve data.
Figure 18.2: Use the AS clause to create an alias for any column.
Figure 18.3: Limit the retrieved data by specifying columns.
Figure 18.4: The DISTINCT predicate returns a unique list of 21 countries.
Figure 18.5: The DISTINCT predicate returns unique records, not just values.
Figure 18.6: Use the TOP predicate to return a portion of records.
Figure 18.7: The ASC keyword reverses the ORDER BY order.
Figure 18.8: The TOP predicate also returns a percentage of records.
Figure 18.9: Without the ORDER BY clause, the TOP predicate makes little sense.
Figure 18.10: Use the WHERE clause to filter records.
Figure 18.11: Use an AND or OR operator to include more than one condition in a WHERE clause.
Figure 18.12: The WHERE clause can handle column references that aren't included in the SELECT clause.
Figure 18.13: The ORDER BY clause sorts a text column alphabetically.
Figure 18.14: The ORDER BY clause can sort by more than one column.
Figure 18.15: A simple GROUP BY clause can generate results similar to a sort.
Figure 18.16: Use GROUP BY to define a group you want to evaluate using an Aggregate function.
Figure 18.17: The WHERE clause eliminates records before they're grouped by the GROUP BY clause.
Figure 18.18: The HAVING clause eliminates dates that had two or fewer orders to show for the day.
Figure 18.19: You can combine the WHERE and HAVING clauses.
Figure 18.20: Use UPDATE to change existing entries.
Figure 18.21: We changed the Title entries from Sales Representative to Account Executive.
Figure 18.22: The DELETE statement removes eight records from the Products table.
Figure 18.23: No records in the Products table have been discontinued.
Figure 18.24: After creating a new products table, run a SELECT statement to view the records.
Figure 18.25: We copied just one product to the new table.
Figure 18.26: SQL returns an error message if the table structures don't match.
Figure 18.27: Insert all the shipper records into the Shippers table.
Figure 18.28: We inserted three new records in the Shippers table.
Figure 18.29: Use INSERT INTO to add a new record to a table.
Figure 18.30: We added a new shipper record to the Shippers table.
Figure 18.31: We'll convert this Access grouped query to a crosstab.
Figure 18.32: Use TRANSFORM and PIVOT to convert a GROUP BY query to a crosstab.
Figure 18.33: This simple query returns the latest order date for each employee.
Figure 18.34: The subquery can handle the OrderID column.
Figure 18.35: Use your system's concatenation character to combine data.

Chapter 19: Getting the Data

Figure 19.1: Viewing dynamic pages in Design mode
Figure 19.2: Viewing dynamic pages in a web browser
Figure 19.3: Viewing dynamic pages in Live Data view
Figure 19.4: The Edit Sites dialog box
Figure 19.5: The ASP website testing server configuration
Figure 19.6: The varQuery- String and varForm output line
Figure 19.7: The Data View Settings dialog box
Figure 19.8: The LiveData view of varQueryString
Figure 19.9: The varForm Live Data Settings dialog box
Figure 19.10: The Live Data view of varForm
Figure 19.11: Live Data View of application, session, and cookie variables
Figure 19.12: The Recordset dialog box
Figure 19.13: The Recordset dialog box in Advanced mode
Figure 19.14: The final simple Recordset configuration
Figure 19.15: Create an SQL statement in the Recordset dialog box in Advanced mode
Figure 19.16: The Test SQL Statement dialog box
Figure 19.17: The Stored Procedure Properties dialog box
Figure 19.18: The Command dialog box
Figure 19.19: The final configuration of the ASP Command Server Behavior
Figure 19.20: The ASP.NET Stored Procedure Server Behavior
Figure 19.21: The ASP.NET Edit Parameter dialog box
Figure 19.22: The ASP.NET Build Value dialog box
Figure 19.23: The ASP.NET Edit Parameter dialog box with generated code
Figure 19.24: The JSP Callable (Stored Procedure) Server Behavior
Figure 19.25: Setting a runtime value in the Callable (Stored Procedure) Server Behavior
Figure 19.26: The ColdFusion Stored Procedure dialog box
Figure 19.27: The ColdFusion Add Parameter dialog box
Figure 19.28: The ColdFusion Edit Stored Procedure Variable dialog box
Figure 19.29: The Dynamic Text dialog box
Figure 19.30: The Data Source view of the Select Image Source dialog box
Figure 19.31: Attach dynamic data to HTML attributes through the Bindings panel
Figure 19.32: Creating a table for the Repeat Region Server Behavior
Figure 19.33: The Repeat Region Server behavior dialog box
Figure 19.34: The live data results of the Repeat Region Server Behavior
Figure 19.35: The Dynamic Table dialog box
Figure 19.36: The live data results of the Dynamic Table Server Behavior
Figure 19.37: The Recordset Navigation Bar Server Behavior dialog box
Figure 19.38: The Recordset Navigation Bar Server Behavior
Figure 19.39: The Recordset Navigation Status Server Behavior
Figure 19.40: The browser result of the Recordset Navigation Status Server Behavior

Chapter 20: Building Update Forms

Figure 20.1: This form elicits feedback for an e-mail message.
Figure 20.2: You can also add a form by clicking the Form control on the Forms tab.
Figure 20.3: In the Tag Editor dialog box, you can specify the properties for your <form> tag.
Figure 20.4: Dreamweaver MX adds a dashed red line to indicate the form boundaries.
Figure 20.5: You set these options to control how your form will look and behave.
Figure 20.6: You set these options to control the language settings of the form.
Figure 20.7: Even forms have events associated with them.
Figure 20.8: The Insert menu lets you add various form controls.
Figure 20.9:   The Forms tab of the Insert bar lets you quickly add controls by clicking the proper icon.
Figure 20.10: The Radio Group dialog box lets you quickly add a formatted group of radio buttons to your form.
Figure 20.11: We've changed the label and value for each button to suit our application's needs.
Figure 20.12: Dreamweaver MX will automatically put the button group in a table for you.
Figure 20.13: The Jump Menu control lets you quickly add a drop- down menu to your pages.
Figure 20.14: Our menu includes links to booksellers.
Figure 20.15: We've defined a recordset for our insert page.
Figure 20.16: The Dynamic Table object will save you time when displaying records from a table.
Figure 20.17:   The Dynamic Table dialog box lets you specify settings for the Dynamic Table you're about to add to your form.
Figure 20.18: We've added the Dynamic Table to our form.
Figure 20.19: Dreamweaver MX created the code that caused our data to repeat.
Figure 20.20: We're adding new rows to the table to accommodate the Navigation bar.
Figure 20.21: Dreamweaver MX jumps to the selected object in the Code window.
Figure 20.22: We're making room for the Navigation bar.
Figure 20.23: Insert the Navigation bar into the table.
Figure 20.24: You use the options in the Recordset Navigation Bar dialog box to control the appearance of your Navigation bar.
Figure 20.25: Dreamweaver MX inserts a placeholder guide in the page.
Figure 20.26: Dreamweaver MX includes a status bar that you can quickly drop into your pages to show where the record pointer is within the table.
Figure 20.27: Your final table should look similar to ours, with the Navigation bar and status bar at the bottom.
Figure 20.28: Save time and effort by letting Dreamweaver MX create an insertion form for you.
Figure 20.29: In the Record Insertion Form dialog box, you specify all the properties necessary to set up a form for inserting data.
Figure 20.30: Our update form now has a means of allowing a user to add a new record to the table.
Figure 20.31: We've added an Update column to our table.
Figure 20.32: Go To DetailPage lets us create a dynamic link to another page.
Figure 20.33:   You can choose which field to send as a URL parameter in the Go To Detail Page dialog box.
Figure 20.34: We've added an update link using the Go To Detail Page Server Behavior.
Figure 20.35: This is the recordset definition for our update page.
Figure 20.36: Our update page is ready.
Figure 20.37: "Selfhelp" is misspelled.
Figure 20.38: Click Update to open the Update Record window, and correct the text.
Figure 20.39: Open the BookCategory.asp page in a browser, and see that indeed the spelling of the category changed.
Figure 20.40: Our recordset for our delete page is similar to the update page recordset.
Figure 20.41: We're manually creating a display for the delete page.
Figure 20.42: Your Delete Record definition should resemble this one.
Figure 20.43: The Submit button's events are hidden in the Tag Editor dialog box.
Figure 20.44: Dreamweaver MX provides a behavior that lets us jump to a URL.
Figure 20.45: The confirmation message after clicking the Delete button

Chapter 21:   Building Master/Detail Page Sets

Figure 21.1: The Master/Detail modelDatabase
Figure 21.2: The Recordset dialog box
Figure 21.3: The Insert Master- Detail Page Set dialog box
Figure 21.4: Viewing the results of Master.asp
Figure 21.5: Viewing the results of Detail.asp
Figure 21.6: The Recordset dialog box
Figure 21.7: The BookID Dynamic Text dialog box
Figure 21.8: The Title Dynamic Text dialog box
Figure 21.9: The Repeat Region dialog box
Figure 21.10: Viewing the result of the Detail2.asp
Figure 21.11: The JSP Recordset dialog box
Figure 21.12: The JSP Insert Master-Detail Page Set dialog box
Figure 21.13: The JSP Recordset dialog box
Figure 21.14: The browser result for Master.jsp
Figure 21.15: The browser result for Detail.jsp
Figure 21.16: The Recordset dialog box
Figure 21.17: The Master Detail Page Set dialog box
Figure 21.18: The browser result of Master.cfm
Figure 21.19: The Detail.cfm Recordset dialog box
Figure 21.20: The browser result of Detail.cfm
Figure 21.21: The DataSet dialog box
Figure 21.22: The DataGrid dialog box
Figure 21.23: The Hyperlink Column dialog box
Figure 21.24: The browser result of Master.aspx
Figure 21.25: The browser result of Detail.aspx
Figure 21.26: The PHP recordset
Figure 21.27: The Dynamic Table dialog box
Figure 21.28: The Dynamic Table browser result
Figure 21.29: The browser results of Master.php
Figure 21.30: Create a filter for the CategoryID URL parameter.
Figure 21.31: Create a filter for the CategoryID URL parameter
Figure 21.32: The browser result for Detail.php

Chapter 22: Searching with Dreamweaver MX

Figure 22.1: A simple form starts our search engine.
Figure 22.2: The Recordset dialog box effectively acts as our search filter.
Figure 22.3: Add a Dynamic Table to display the search results.
Figure 22.4: Set the options for your Dynamic Table.
Figure 22.5: Dreamweaver MX has added to our page a table to display the record list.
Figure 22.6: Our simple search form
Figure 22.7: We found all the records matching "Mouse".
Figure 22.8: When creating ASP pages, Dreamweaver MX offers Request.Form variables as a new binding type.
Figure 22.9: We've added a new variable binding to our page.
Figure 22.10: We're adding a search reminder for the user.
Figure 22.11: Our modified search results page
Figure 22.12: We're adding multiple fields upon which to search.
Figure 22.13: Click the Advanced button to open the advanced version of the Recordset dialog box.
Figure 22.14: The advanced options in the Recordset dialog box.
Figure 22.15: After adding the new search criteria to your query, your advanced Recordset dialog box should look similar to this.

Chapter 23: Using Templates

Figure 23.1: Choose a page category and type.
Figure 23.2: Identify the site to which you're adding the template.
Figure 23.3: You can access a template in the Assets window.
Figure 23.4: Dreamweaver MX lists templates in the Assets window.
Figure 23.5: The Templates tab displays all your templates.
Figure 23.6: Choose a site, and then specify a template.
Figure 23.7: Insert the fence graphic.
Figure 23.8: Insert the banner graphic below the fence graphic.
Figure 23.9: After adding the graphics, save the template.
Figure 23.10: Enter text directly into the page to lock it, meaning no one can edit it outside the template.
Figure 23.11: Use the Insert bar to quickly insert regions.
Figure 23.12: In the Name box, enter a name for the new editable region.
Figure 23.13: Dreamweaver MX highlights the new region's border.
Figure 23.14:   Add a total of three editable regions to the template.
Figure 23.15: Add a repeating region for items you might want to repeat.
Figure 23.16: Define a two-column repeating table.
Figure 23.17: Add a repeating table for monthly contributors.
Figure 23.18: Name and determine whether the optional regional is displayed by default in the template-based page.
Figure 23.19: You can define the optional region's visibility to be based on a parameter or an expression you enter.
Figure 23.20: Insert a parameter tag so a page author can determine whether the price content is displayed.
Figure 23.21: Enter the price per issue in the optional region.
Figure 23.22: Use the Properties Inspector to quickly modify a region's properties.
Figure 23.23: Click the Edit button to open the New Optional Region dialog box.
Figure 23.24: Be sure to select the appropriate tag.
Figure 23.25: Name the new attribute and modify the default setting if necessary.
Figure 23.26: We replaced the original alignment tag with an editable tag.
Figure 23.7: Save the new page.
Figure 23.28: Add content to the editable regions of the repeating table.
Figure 23.29: Enter a contributor in the repeating region.
Figure 23.30: Add a second row to the repeating table.
Figure 23.31: eselecting the Show OptionalPrice option hides the optional region.
Figure 23.32: After adding unique content, display your template-based page in a browser.
Figure 23.33: Scroll down to see the rest of the page.
Figure 23.34: Create a recordset that will retrieve the dynamic text.
Figure 23.35: Add the <Template Info> tag to the <head> section.
Figure 23.36: Select the field that contains the data you want to display.
Figure 23.37: Our template-based page displays data from our Books database.

Chapter 24: Dreamweaver MX Add-Ins

Figure 24.1: Launch the Macro- media Extension Manager from Dreamweaver MX's Commands menu.
Figure 24.2: You must have version 1.5 or later of Macromedia's Extension Manager in order to use extensions with Dreamweaver MX.
Figure 24.3: The Macromedia Extension Manager lets you install and control the extensions you add to Dreamweaver MX.
Figure 24.4: Extensions come in Macromedia Extension Packages, files with a .mxp extension.
Figure 24.5: You must accept the disclaimer in order to install a new extension.
Figure 24.6: Our installation is a success.
Figure 24.7: Extensions can show up anywhere in Dreamweaver MX, depending on their type and function.
Figure 24.8: Extension Manager lets you temporarily disable an extension.
Figure 24.9: You can also permanently remove an extension in Extension Manager.
Figure 24.10: The Macromedia Exchange is the best source for extensions for all your Macromedia products.
Figure 24.11: You'll have to log in to use the Macromedia Exchange.
Figure 24.12: More of the Macromedia Exchange main page
Figure 24.13: The rest of the Exchange main page
Figure 24.14: Quickly find extensions by choosing a category from the Browse Extensions drop-down list box.
Figure 24.15: The Advanced Search page lets you find Dreamweaver MX-specific extensions.
Figure 24.16: The extension information page for the Abbreviation and Acronym extension
Figure 24.17: Check Form gives you more control over validating your forms.
Figure 24.18: Cube Stores installs new menus and object panels, as well as a help system to get you started quickly.
Figure 24.19: Context Help Toolbar is one of the handiest extensions you'll find. It provides contextual help on just about every tag DreamweaverMX can handle.
Figure 24.20: Favorites Menu gives you quick access to files you use frequently.
Figure 24.21: Drop Down Menu Builder for IE lets you quickly build drop-down menus for Internet Explorer.
Figure 24.22: You can quickly size your table cells with this extension.
Figure 24.23: This extension adds a tab to the Insert bar that Dreamweaver MX was missing- the CFML Form tab.
Figure 24.24: Go To Line Number (both versions) lets you immediately jump to a line number in the Code View window.
Figure 24.25: This extension closes all open documents.
Figure 24.26: Quickly prevent right-clicks in your web pages usingNo Right-Click.

Mastering Dreamweaver MX Databases
Mastering Dreamweaver MX Databases
ISBN: 078214148X
EAN: 2147483647
Year: 2002
Pages: 214 © 2008-2017.
If you may any questions please contact us: