Step 11: Next up is question number five. Here we will build a list of four possible answers or input prompts for the participant to select from. We'll use the input type One of several options to
handle the question effectively. I'll cut and paste the four possible responses into the input prompt dialog box. I use the field label prompt MCPemploy to help with the construction of a confirmation form, and mapping of fields in the database where we will store the results,
discussed later in this tutorial. Finally, I chose a simple drop down menu for industry classification, since most folks that use the Web have probably encountered such a prompt on surveys before. However, use of drop down menus should be limited in a survey. Keep it simple.
Step 12: The next question in the survey requires an integer field prompt similar to Step 9, since it deals with the question of annual salaries
of MCPs. In this case, we'll use a six figure number prompt because some MCPs and MOUSs make this amount of income. I used the field label MCPsalary to identifiy it.
Note: As a reminder, and based on the first question of the survey, you don't have to be a MCP or MOUS
to take this survey.
Step 13: Next, working with question number seven, we create an integer prompt to collect data on the rate charged by independent IT consultants. So we create an integer field prompt with a maximum
of 3 digits in length, since most freelance consultants charge anywhere from $25 per hour as SOHO (Small Office/Home Office) IT specialist to $180 per hour for developing complex applications using programming languages like Microsoft C++® and Microsoft Visual Basic®. With this input
prompt I used MCP Hourly for the field label. Once completed, I click Next to return to the Add Input Type dialog box.
Figure 9 Building the list of questions for a survey form.
Step 14: The next question for our survey is a simple yes or no answer to a controversial question regarding the future of computing for network engineers and administrators. I choose the input
type Boolean to manage this survey question appropriately. The Boolean is a simple yes/no, true/false prompt that requires two steps to complete. First you cut and paste your question in the initial prompt, and then supply the logic to it in the following step or screen as show in
Figure 10. I chose the middle option, with yes/no as the prompt with radio buttons as the mechanism for handling question. I used the field or variable name Webservices to help in identification of the field for the confirmation form and database. I click, Next, to return to add the
next question in the survey.
Tip: Radio buttons help survey participants understand inherently that it's either one answer or another, and forces them to choose between two or more items in a list.
Figure 10 Configuring Boolean logic for an input prompt.
Step 15: The next survey question regards technical instruction and what methods IT professionals and developers use to obtain the training they need to keep abreast in their field. There are five
possible answers or input prompts to build for this step. So again, we'll choose the Any of Several Options input type and label the variable TrainingOptions in the first step in the process, click Next to proceed to step two of Add Input Type where I will cut and paste the
input responses from the draft survey provided by the client directly into the Input Type dialog box of the Form Page wizard. Finally, I'll click Next to add the next question or prompt in the survey form.
Essentially, you cycle through it at various stages to build an interactive form for a Web site. By the time you added five or six questions you begin to get the hang of it and can speed up adding more questions. However, this is only stage one of the form
development. You will want to tweak the survey after you are done with the wizard and of course test before publishing to the Web.
The final steps of building our interactive Web survey using Forms Wizard include more questions to add to the survey and a few finishing screens before moving on to the subject of storing results of the form in an Access database for later retrieval.