End User Recipe: Meeting Conflict | Macromedia Dreamweaver 8 Recipes

After the user submits the meeting request, the data source is checked to see if a conflicting meeting is already scheduled. If so, the meeting_conflict page is displayed with an error message and details of the existing meeting. From this page, the user is advised to return to the meeting_request form and modify the request.

All the data-driven elements on the meeting_conflict page come from a single recordset. The recordset's filter is based on a URL parameter passed by the meeting_request page.

Step 1: Implement Meeting Conflict Design

No form is needed for the meeting_conflict page; only a series of dynamic text elements are used.

Create a basic dynamic page, either by hand or derived from a template.

In the ConferenceRoomScheduler folder, locate the folder for your server model and open the meeting_conflict page found there.

Add a table to the content region of your page to contain the interface elements for the application.

From the Snippets panel, drag the Recipes > ConferenceRoom > Wireframes > Meeting Conflict - Wireframe snippet into the Content editable region.

Add the table area to hold the dynamic text for the conflicting record details and an informative error message.

Place your cursor in the row below the words MEETING CONFLICT and insert the Recipes > ConferenceRoom > ContentTables > Meeting Conflict - Content Table snippet [r3-5].

r3-5.

Recipe Variation: Adding a Return to Form Button

Although it's perfectly fine to advise the user to click his or her browser's Back button to return to the previous form, some developers might want to provide a dedicated button for this functionality. As described in Recipe 1, "User Login," a bit of JavaScripthistory.back()added to the onClick event of a form button, either directly in the tag or through the Call JavaScript behavior, works quite well.

Save the file.

Step 2: Add Database Components

Only one data source is required for this page: a recordset containing only the conference details of the just-entered record. For ASP and ColdFusion, this recordset uses a view that combines the Conferences and Rooms tables as well as two formatted data source fields, StartDate and StartTime, and one calculated one, ConferenceEnd. Here's the SQL statement used to construct the view:

[View full width]
SELECT Conferences.ConferenceID, Rooms.RoomName, Rooms.RoomID, Rooms.RoomDescription,  Conferences.ConferenceName, Conferences.ConferenceDescription, Conferences.ConferenceStart , Conferences.ConferenceDuration, Conferences.ConferenceBy, Format([ConferenceStart],'h:nn  ampm') AS StartTime, Format([ConferenceStart],'m/dd/yyyy') AS StartDate, DateAdd('n', ([ConferenceDuration]*60),[ConferenceStart]) AS ConferenceEnd FROM Conferences INNER JOIN Rooms ON Conferences.ConferenceRoom = Rooms.RoomID;

Because Dreamweaver makes views as accessible as tables, this complex SQL statement can be added through the simple Recordset dialog for ASP and ColdFusion developers.

PHP users must take a different route, because views are unsupported in MySQL.

For ASP and ColdFusion

From the Bindings panel, choose Add (+) and select Recordset (Query).

In the simple Recordset dialog, enter an appropriate name.

Enter Conferences in the Name field.

Select the data source connection.

Choose Recipes from the Connection (Data Source) list.

Choose the needed view.

From the Tables list, select ConferenceDisplay.

Leaving the Columns option set to All, set the four Filter list elements like this:

`ConferenceID`	`= (Equals)`
`URL Parameter`	`ID`

Keep the Sort option set to None and click OK to close the dialog.

For PHP

PHP users have two hurdles to overcome when defining this recordset. First, we'll have to compensate for the lack of view support in MySQL. This is accomplished fairly easily by using a custom SQL statement. Second, Dreamweaver's implementation of PHP code requires a work-around. Unfortunately, the Dreamweaver MySQL engine does not support complex date and time formatting, such as DATE_FORMAT (conferences.ConferenceStart,'%m/%d/%Y'), which converts the string returned by the ConferenceStart field to a month/day/year format. To get around this issue, we'll insert a pseudo recordset and then replace the code that Dreamweaver writes a bit later.

To prepare for this step, first place your cursor in a text string in Design view. Then, right-click (Control-click) the Recipes > ConferenceRoom > SQL > Meeting Conflict - PHP SQL Statement snippet and select the Copy Snippet command.

From the Bindings panel, choose Add (+) and select Recordset (Query) from the list.

In the advanced Recordset dialog, enter an appropriate name for the recordset.

Enter Conferences in the Recordset field.

Choose the data source.

Select Recipes from the Connections list.

Enter the proper SQL statement:

In the SQL area, press Ctrl-V (Command-V) to paste the code copied from the snippet.

[View full width]
SELECT conferences.ConferenceID, rooms.RoomName,  rooms.RoomID, rooms.RoomDescription, conferences .ConferenceName, conferences.ConferenceDescription,  conferences.ConferenceStart, TIME_FORMAT (conferences.ConferenceDuration,'%k:%i') AS  ConferenceDuration, conferences.ConferenceBy,  DATE_FORMAT (conferences.ConferenceStart,'%k:%i  %p') AS StartTime, DATE_FORMAT(conferences .ConferenceStart,'%c/%d/%Y') AS StartDate,  (INTERVAL HOUR(conferences.ConferenceDuration) HOUR  + INTERVAL MINUTE(conferences.ConferenceDuration)  MINUTE + conferences.ConferenceStart) AS ConferenceEnd FROM conferences, rooms WHERE conferences.ConferenceRoom = rooms.RoomID  AND conferences.ConferenceID = IDParam

In the Variables section, choose Add (+) and enter the following details in the Add Parameter dialog:

`Name:`	`IDParam`
`Default Value:`	`0`
`Run-time Value:`	`$_GET['ID']`

Click OK to close the dialog and insert the recordset.

Save your page.

This temporary recordset will allow us to complete the next step in the recipebinding the data to the pageafter which we will replace the temporary code with the actual code.

Step 3: Data Binding Process

Data binding for the meeting_conflict page is very straightforward. After the recordset has been defined, all that remains to complete that operation is to put seven dynamic text elements in place.

From the Bindings panel, expand the Conferences recordset.

Place the data source fields onto the page in their respective areas:

	Drag ConferenceName to the cell next to the Meeting Name label.
	Drag ConferenceBy to the cell next to the Meeting Owner label.
	Drag ConferenceDescription to the cell next to the Meeting Description label.
	Drag StartDate to the cell next to the Meeting Date label.
	Drag StartTime to the cell next to the Start Time label.
	Drag ConferenceDuration to the cell next to the Duration label.
	Drag RoomName to the cell next to the Conference Room label.

Save the page when you're done.

To test this page, browse to meeting_request and enter information for a new meeting that conflicts with an existing meeting. Remember, the room as well as the date and time must conflict to display the meeting_conflict page [r3-6].

r3-6.