Home > Articles > Data > SQL Server

📄 Contents

  1. Introduction
  2. Sample Database-Driven Web Application: Web Site Guest Book
  3. Outline for the Remaining Tutorials

Sample Database-Driven Web Application: Web Site Guest Book

To understand how HTML forms, databases, Active Server Pages, and SQL fit together, let's analyze the classic example of a database-driven Web page: a Web site guest book. You've probably signed a guest book on a Web site at some point while Web surfing. The typical Web site guest book usually asks for your name, email address, age, gender, and a comment (see Figure 1 for an example).

Figure 1 Sample HTML guest book form.

When you fill out the form and click the submit button—usually labeled SIGN MY GUEST BOOK or some equivalent—you're typically brought to a page that thanks you for filling out the guest book, or one that shows your guest book entry along with those of all the other users who signed the guest book (see Figure 2).

NOTE

You can experiment with the guest book above by visiting http://www.ProfessorF.com/informIT/guestbook.html)

Figure 2 Contents of the guest book, displayed after clicking the SIGN MY GUEST BOOK button.

The big question is what happens between the time you click the SIGN MY GUEST BOOK button and the time the guest book's content is displayed on the screen. If you know the answer to that question, you know how databases and SQL interact with HTML forms and Active Server Pages. If you don't know the answer, please read on.

Behind the Scenes: How HTML Forms, Active Server Pages Scripts, Structured Query Language (SQL), and Databases Interact

When a user fills out a form and clicks the submit button, the information that the user entered (for example, Barney Rubble, barney@roll.com, 34, male, I Love Betty, and so on) is sent to the Web server (such as http://www.ProfessorF.com) along with the name of an Active Server Pages file that the server should execute to process the user's data (for example, insert.asp). The actual name of the Active Server Pages file is hidden inside the HTML source file for the guest book. If your browser is Microsoft Explorer, you can find this name by going to your browser's View menu and selecting the Source menu item. A screen will then pop up. Scroll through this screen looking for a <FORM> tag. One of the parameters for the <FORM> tag is labeled ACTION, and its value is the name of the Active Server Pages file that the Web server should execute (in Listing 1, that's insert.asp):

Listing 1 Portion of the Source Code for the Guest Book Form (guestbook.html)

...
<FORM METHOD=POST ACTION="insert.asp">
...
</FORM>
...

The Active Server Pages (ASP) file is simply a text file, just like the HTML file used to bring up the Guest Book form. One noticeable difference is that, instead of having a filename ending in .html, such as guestbook.html, an ASP file ends in .asp, such as insert.asp. You create an ASP file using your favorite text editor—we like using Notepad—and upload it to the Web server the same way you would create an HTML file and upload that to a server—for example, using FTP. The main difference is that an Active Server Pages file can contain both HTML and Visual Basic code. The latter is a subset of the full-blown Visual Basic language, and is known as Visual Basic Script, or VBScript for short. Because an ASP file can contain both HTML and programming code, it's often referred to simply as a script. We'll use the terms ASP file and ASP script interchangeably. Because your Web server and not the user's Web browser executes the script, ASP scripts are also known as server-side scripts. In contrast, the Web browser typically executes JavaScript, so JavaScript is often referred to as a client-side script.

Back to our example. The Web server passes the user's information to the ASP script (insert.asp, also known as the insert script), which first opens a database (see Listing 2, step 1), and then places the user's data into the database (step 2). To place the user's information into the database, the ASP code must communicate with the database in a special language known as Structured Query Language (SQL), as shown in the bold text in step 2. After the ASP script inserts the user's information into the database, the final step (step 3) is to call a retrieve script, which displays the database information; in this example, that's the guest book.

Listing 2 Portion of the ASP Insert Script (insert.asp)

...
'
'STEP 1. Open the database
'
conn.open("DBQ=" & server.mappath("visualtutorial.mdb")    & _
     ";Driver={Microsoft Access Driver (*.mdb)};")
...
'
'STEP 2. Use SQL to communicate the user's information
'     to the database.
'
conn.execute("insert into GuestBook "             & _
       "(name, email, hideEmail, age, gender, comment) " & _
       "Values ("                    & _
       "'" & v_name   & "',"             & _
       "'" & v_email   & "',"             & _
       " " & v_hideEmail & " ,"             & _
       " " & v_age    & " ,"             & _
       "'" & v_gender  & "',"             & _
       "'" & v_comment  & "')")
conn.close
set conn=nothing
'
'STEP 3. Call another ASP script (retrieve.asp) to display guestbook
'
response.redirect("retrieve.asp")
...

TIP

We mentioned that an ASP script could contain both VBScript and HTML code. Note, however, that the insert script in Listing 2 only has VBScript—and it's also possible to have an ASP file containing just HTML.

The ASP retrieve script, retrieve.asp, combines VBScript and HTML. The script starts off by opening the database (see Listing 3, step 1) and then sends an SQL command to retrieve the entire contents of the guest book (step 2). The script then intersperses VBScript and HTML to format the contents of the guest book. You can tell the difference between the HTML and VBScript because the VBScript is contained within <% and %> symbols.

Listing 3 Portion of the ASP Retrieve Script (retrieve.asp)

...
'
' Step 1. Open up the database
'
conn.open("DBQ=" & server.mappath("visualtutorial.mdb") & _
     ";Driver={Microsoft Access Driver (*.mdb)};")
...
<FONT style="font-size:18pt">
<FONT COLOR=MAROON><B>Cool People Who Signed My Guest Book!</B></FONT>
</FONT>
...
'
' Step 2. Use SQL to retrieve all the entries from
'     the database's GuestBook table
'
<% set rs=conn.execute("select * from GuestBook") %>
'
' Display the Guest Book using HTML to format the information
'
<TABLE BORDERCOLOR=MAROON CELLSPACING=0 BORDER=1><TR><TD>
<TABLE CELLSPACING=0>
<TR BGCOLOR=MAROON>
<TD ALIGN=CENTER><B><FONT COLOR=TAN>Date</FONT></B></TD>
<TD ALIGN=CENTER><B><FONT COLOR=TAN>Email</FONT></B></TD>
<TD ALIGN=CENTER><B><FONT COLOR=TAN>Name</FONT></B></TD>
<TD ALIGN=CENTER><B><FONT COLOR=TAN>Age</FONT></B></TD>
<TD ALIGN=CENTER><B><FONT COLOR=TAN>Gender</FONT></B></TD>
<TD ALIGN=CENTER><B><FONT COLOR=TAN>Comment</FONT></B></TD>
</TR>
<%
dogrey=false
do while not rs.eof
%>
  <% if not(dogrey) then %>
   <TR>
  <% else %>
   <TR bgcolor=lightgrey>
  <% end if %>
  <% dogrey=not(dogrey) %>
  <TD>
   <%=month(rs("dateposted"))%> /
   <%=day(rs("dateposted"))%>  /
   <%=year(rs("dateposted"))%>
  </TD>
  <TD><%=rs("email")%>  </TD>
  <TD><%=rs("name")%>  </TD>
  <TD><%=rs("age")%>   </TD>
  <TD><%=rs("gender")%> </TD>
  <TD><%=rs("comment")%> </TD>
  </TR>
<%
rs.movenext
loop
rs.close
set rs=nothing
%>
</TABLE></TD></TR>
</TABLE>
...

In our example, after the retrieve.asp script executes, the user sees the contents of the guest book (refer to Figure 2).

How the Pieces Fit Together Graphically

The diagram in Figure 3 summarizes the preceding discussion. The HTML form sends the user's information to an ASP insert script, which uses SQL to insert the information into a database. An ASP retrieve script uses SQL to read data from the database, which it formats using HTML, and sends that HTML to the user's browser. If you try to view the source for this HTML, you won't see any VBScript at all, since all code is executed on the Web server and the code only sends HTML to the browser.

Figure 3 Graphical depiction of how the HTML form, ASP insert (store) script, database, and ASP retrieve script fit together.

To summarize, when you create a database-driven Web application, you always develop four pieces:

  • A form in HTML to get information from a user (such as guestbook.html)

  • An insert script in Active Server Pages to put the user's information into the database (such as insert.asp)

  • A database to store the information (such as visualtutorial.mdb)

  • A retrieve script in Active Server Pages to get information out of the database and display it on the user's browser (such as retrieve.asp)

You upload all these pieces to your Web server, just as you would your HTML files. Our example put these pieces in separate files, but it's common to combine the pieces; for example, the HTML form can be put in the same file as the insert script.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020