Home > Articles > Web Services > XML

Sams Teach Yourself XML in 21 Days

Sep 16, 2005

📄 Contents

␡

⎙ Print

< Back Page 251 of 288 Next >

Recommended Book 

Sams Teach Yourself XML in 21 Days, 3rd Edition

Learn More Buy

Storing Databases as XML

Microsoft has added a great deal of XML support to its database products—far more than any other provider out there, so like it or not, we're in Microsoft territory here. In particular, Microsoft's ADO.NET database protocol uses XML to send data back and forth between databases and applications.

For example, let's examine how to use a Visual Basic .NET application to interact with a database by using SQL Server and see how the data is actually transferred with XML. Figure 20.3 shows a step in the process of creating a new Visual Basic .NET Windows application named ch20_03.

Figure 20.3 Creating a Visual Basic .NET Windows application.

Figure 20.4 shows the new Windows application that we create, complete with the two buttons Store XML Data and Read XML Data. Because ADO.NET datasets are sent back and forth by using XML, we can create a dataset when the user clicks the Store XML Data button and store it in XML; then we can create a new dataset by using that XML data when the user clicks the Read XML Data button. After we create the second dataset, we'll bind that data to a data grid control, so let's add a data grid to the Windows form now, as shown in Figure 20.4.

Figure 20.4 Creating the ch20_03 application.

We'll need a connection to a data source, and in this case we can use Microsoft SQL Server, which is often used in .NET data work. In this case, we'll use a data connection to the pubs SQL Server sample database and extract the data from the employee table in that database. To create that data connection, right-click the Data Connections icon in the Visual Basic .NET Server Explorer (the tab for this tool appears at the left in the Visual Basic .NET development environment, as shown in Figure 20.4), and select the Add Connection item; or select Tools, Connect to Database. In either case, the Data Link Properties dialog box appears.

In the Data Link Properties dialog box, enter the name of the server you want to work with, as well as the login name and password, if applicable—or select the Windows NT integrated security option if your application and SQL Server are on the same machine. Next, choose a database to work with by using either the Select the Database on the Server option or the Attach a Database File as a Database Name option. In this case, we'll use the pubs sample database that comes with SQL Server, so let's select the first option and choose the pubs database. Then you need to click OK to close this dialog box.

This new data connection appears in the Visual Basic .NET Server Explorer. Now that we've created a data connection to the pubs database, we can drag an OleDbDataAdapter control from the Visual Basic .NET toolbox to the Visual Basic .NET form we're creating; this opens the Data Adapter Configuration Wizard. You need to click Next to move to the second pane of this wizard, as shown in Figure 20.5. Then select the data connection to the pubs database (it is named STEVE.pubs.dbo on the machine this example is being developed on, as shown in the figure), and then click Next twice, to open the Data Adapter Configuration Wizard's fourth pane.

Figure 20.5 Connecting to the pubs database.

To indicate that you want to connect to the employee table, you need to click the Query Builder button in the fourth pane of the wizard, select the employee item in the Add Table dialog box that appears, click the Add button and then the Close button. The Query Builder appears, as shown in Figure 20.6.

Figure 20.6 The Query Builder.

The Query Builder lets us generate the SQL needed to extract the employee table from the pubs database. To generate that SQL, click the All Columns check box in the employee table's window, as shown in Figure 20.6, and then click OK. As you can see in the Data Adapter Configuration Wizard in Figure 20.7, this generates the following SQL statement:

SELECT
    employee.*
FROM
    employee"

Figure 20.7 A new SQL statement in the Query Builder.

Now you need to click Next and then Finish to complete the creation of the data adapter you'll need to connect to the employee table. This creates both an OleDbDataAdapter object and an OleDbConnection object.

The connection object will maintain the connection to SQL Server, and the adapter object will be responsible for activating the connection and retrieving data. Both connection and adapter objects are important in ADO.NET work. Table 20.1 lists the significant properties of the OleDbDataAdapter objects, and Table 20.2 lists the significant methods of these objects. Table 20.3 lists the significant properties of the OleDbConnection objects, and Table 20.4 lists the significant methods of these objects.

Table 20.1. Significant Public Properties of `OleDbDataAdapter` Objects

Property	Description
`DeleteCommand`	Returns or sets the SQL for deleting records.
`InsertCommand`	Returns or sets the SQL for inserting new records.
`SelectCommand`	Returns or sets the SQL for selecting records.
`UpdateCommand`	Returns or sets the SQL for updating records.

Table 20.2. Significant Public Methods of `OleDbDataAdapter` Objects

Method	Description
`Fill`	Adds rows to or refreshes rows in a dataset to make them match the rows in a data store.

Table 20.3. Significant Public Properties of `OleDbConnection` Objects

Property	Description
`ConnectionString`	Returns or sets the connection string to open a database.
`ConnectionTimeout`	Returns the time to wait while trying to make a connection (in seconds).
`Database`	Returns the name of the database to open.
`DataSource`	Returns the data source (usually the location and filename of the file to open).
`Provider`	Returns the OLE DB provider's name.
`ServerVersion`	Returns the version of the server.
`State`	Returns the connection's current state.

Table 20.4. Significant Public Methods of `OleDbConnection` Objects

Method	Description
`BeginTransaction`	Starts a database transaction.
`ChangeDatabase`	Changes the current database.
`Close`	Closes the connection to the data provider.
`CreateCommand`	Creates an `OleDbCommand` object for this connection.
`GetOleDbSchemaTable`	Returns the current schema table.
`Open`	Opens a database connection.

We're going to connect the employee table to a dataset object so we can access that table's data. To create a dataset based on the data supplied by our OleDeDataAdapter object, you need to select Data, Generate Dataset in Visual Basic .NET. This opens the Generate Dataset dialog box, and you need to click OK to create a new dataset object, DataSet11 (that is, the first object of the automatically generated DataSet1 class). Datasets act as repositories of data in .NET, and they give us direct local access to the data from a data provider. Table 20.5 lists the significant properties of the DataSet class, and Table 20.6 lists the significant methods of the DataSet class.

Table 20.5. Significant Public Properties of the `DataSet` Class

Property	Description
`DataSetName`	Returns or sets the name of the dataset.
`EnforceConstraints`	Returns or sets whether constraint rules are enforced.
`HasErrors`	Indicates whether there are errors in any row in the table.
`Relations`	Gets relation objects that link tables.
`Tables`	Returns tables in the dataset.

Table 20.6. Significant Public Methods of the `DataSet` Class

Method	Description
`AcceptChanges`	Accepts (commits) the changes made to the dataset.
`Clear`	Clears the dataset by removing all rows in all tables.
`Copy`	Copies the dataset.
`GetChanges`	Returns a dataset that contains all changes made to the current dataset.
`GetXml`	Returns the data in the dataset in XML.
`GetXmlSchema`	Returns the XSD schema for the dataset.
`HasChanges`	Indicates whether the dataset has changes that have not yet been accepted.
`Merge`	Merges this dataset with another dataset.
`ReadXml`	Reads data into a dataset from XML.
`ReadXmlSchema`	Reads an XML schema into a dataset.
`RejectChanges`	Rolls back the changes made to the dataset since it was created or since the `AcceptChanges` method was last called.
`Reset`	Resets the dataset to the original state.
`WriteXml`	Writes the dataset's schema and data to XML.
`WriteXmlSchema`	Writes the dataset schema to XML.

Now double-click the Store XML Data button to open the handler function that holds the code that will be executed when the button is clicked:

Private Sub Button1_Click(ByVal sender As System.Object,
        .
        .
        .
End Sub

Begin this code by using the data adapter object to fill the dataset object with data from the employee table:

Private Sub Button1_Click(ByVal sender As System.Object,
    ByVal e As System.EventArgs) Handles Button1.Click
    DataSet11.Clear()

       OleDbDataAdapter1.Fill(DataSet11)
        .
        .
        .
End Sub

Next store the employee table from the dataset as an XML document, data.xml, by using the dataset's WriteXml method:

Private Sub Button1_Click(ByVal sender As System.Object,
    ByVal e As System.EventArgs) Handles Button1.Click
    DataSet11.Clear()
    OleDbDataAdapter1.Fill(DataSet11)
    DataSet11.WriteXml("data.xml")
        .
        .
        .
End Sub

In fact, ADO.NET uses XML and XML schemas to transfer data in .NET, so write the current schema out to a file, dataSchema.xml, as well, by using the WriteXmlSchema method:

Private Sub Button1_Click(ByVal sender As System.Object,
    ByVal e As System.EventArgs) Handles Button1.Click
    DataSet11.Clear()
    OleDbDataAdapter1.Fill(DataSet11)
    DataSet11.WriteXml("data.xml")
    DataSet11.WriteXmlSchema("dataSchema.xml")
End Sub

Now you'll read this XML back in and use it to create a new dataset object. First, create that dataset object by adding this code to the handler method that is called when the Read XML Data button is clicked:

Private Sub Button2_Click(ByVal sender As System.Object,
    ByVal e As System.EventArgs) Handles Button2. Click
    Dim ds As New DataSet()
        .
        .
        .
End Sub

Now use this dataset object's ReadXML method to read the XML document that holds the entire employee table:

Private Sub Button2_Click(ByVal sender As System.Object,
    ByVal e As System.EventArgs) Handles Button2.Click
    Dim ds As New DataSet()

       ds.ReadXml("data.xml")
        .
        .
        .
End Sub

Because you've read the XML holding the employee table back in, bind it to your DataGrid control:

Private Sub Button2_Click(ByVal sender As System.Object,
    ByVal e As System.EventArgs) Handles Button2.Click
    Dim ds As New DataSet()
    ds.ReadXml("data.xml")
    DataGrid1.SetDataBinding(ds, "employee")
End Sub

The DataGrid class lets us display entire database tables in .NET applications, and it's designed to be used in data-aware applications. Table 20.7 lists the significant properties of the DataGrid class, and Table 20.8 lists the significant methods of this class.

Table 20.7. Significant Public Properties of the `DataGrid` Class

Property	Description
`AllowNavigation`	Returns or sets whether navigation is allowed in the data grid.
`AllowSorting`	Returns or sets whether the grid can be sorted when the user clicks a column header.
`AlternatingBackColor`	Returns or sets the background color used in alternating rows.
`BackColor`	Returns or sets the background color of the data grid.
`BackgroundColor`	Returns or sets the color of the nondata sections of the data grid.
`BorderStyle`	Returns or sets the data grid's border style.
`CaptionBackColor`	Returns or sets the caption's background color.
`CaptionFont`	Returns or sets the caption's font.
`CaptionForeColor`	Returns or sets the caption's foreground color.
`CaptionText`	Returns or sets the caption's text.
`CaptionVisible`	Returns or sets whether the caption is visible.
`ColumnHeadersVisible`	Returns or sets whether the parent rows of a table are visible.
`CurrentCell`	Returns or sets which cell has the focus.
`CurrentRowIndex`	Returns or sets the index of the selected row.
`DataMember`	Returns or sets the table or list of data the data grid should display.
`DataSource`	Returns or sets the data grid's data source, such as a dataset.
`FirstVisibleColumn`	Returns the index of the first column visible in the grid.
`FlatMode`	Returns or sets whether the data grid should be shown flat.
`ForeColor`	Returns or sets the foreground color used in the data grid.
`GridLineColor`	Returns or sets the color of grid lines.
`GridLineStyle`	Returns or sets the grid line style.
`HeaderBackColor`	Returns or sets the background color of headers.
`HeaderFont`	Returns or sets the font used for headers.
`HeaderForeColor`	Returns or sets the foreground color of headers.
`Item`	Returns or sets the value in a particular cell.
`LinkColor`	Returns or sets the color of links to child tables.
`LinkHoverColor`	Returns or sets the color of links to child tables when the mouse moves over it.
`ParentRowsBackColor`	Returns or sets the background color of parent rows.
`ParentRowsForeColor`	Returns or sets the foreground color of parent rows.
`ParentRowsLabelStyle`	Returns or sets the style for parent row labels.
`ParentRowsVisible`	Returns or sets whether parent rows are visible.
`PreferredColumnWidth`	Returns or sets the width of the grid columns (in pixels).
`PreferredRowHeight`	Returns or sets the preferred row height.
`ReadOnly`	Returns or sets whether the grid is read-only.
`RowHeadersVisible`	Returns or sets whether row headers are visible.
`RowHeaderWidth`	Returns or sets the width of row headers.
`SelectionBackColor`	Returns or sets the selected cell's background color.
`SelectionForeColor`	Returns or sets the selected cell's foreground color.
`TableStyles`	Returns the table styles in the data grid.
`VisibleColumnCount`	Returns the number of visible columns.
`VisibleRowCount`	Returns the number of visible rows.

Table 20.8. Significant Public Methods of the `DataGrid` Class

Method	Description
`BeginEdit`	Makes the data grid allow editing.
`Collapse`	Collapses child table relations.
`EndEdit`	Ends editing operations.
`Expand`	Displays child relations.
`HitTest`	Coordinates the mouse position with points in the data grid.
`IsExpanded`	Returns whether a row is expanded or collapsed.
`IsSelected`	Returns whether a row is selected.
`NavigateBack`	Navigates to the previous table that was shown in the grid.
`NavigateTo`	Navigates to a specific table.
`Select`	Makes a selection.
`SetDataBinding`	Sets both the `DataSource` and `DataMember` properties. This method is used at runtime.
`UnSelect`	Deselects a row.

Now run this application by selecting Debug, Start. Then, when you click the Store XML Data button, the employee table is stored in an XML document on disk; when you click the Read XML Data button, that XML document is read back into a new dataset object, which is bound to the DataGrid control in this application. Figure 20.8 shows the results, with the employees table, fresh from your XML document, appearing in the data grid.

Figure 20.8 Writing a database table to XML and reading it back in.

Here's what the employee table looks like as stored in XML in your XML document (note that each employee's data is stored in an element named <employee>):

<?xml version="1.0" standalone="yes"?>
<DataSet1 xmlns="http://www.tempuri.org/DataSet1.xsd">
  <employee>
    <emp_id>PMA42628M</emp_id>
    <fname>Paolo</fname>
    <minit>M</minit>
    <lname>Accorti</lname>
    <job_id>13</job_id>
    <job_lvl>35</job_lvl>
    <pub_id>0877</pub_id>
    <hire_date>1992-08-27T00:00:00.0000000-04:00</hire_date>
  </employee>
  <employee>
    <emp_id>PSA89086M</emp_id>
    <fname>Pedro</fname>
    <minit>S</minit>
    <lname>Afonso</lname>
    <job_id>14</job_id>
    <job_lvl>89</job_lvl>
    <pub_id>1389</pub_id>
    <hire_date>1990-12-24T00:00:00.0000000-05:00</hire_date>
  </employee>
  <employee>
    <emp_id>VPA30890F</emp_id>
    <fname>Victoria</fname>
    <minit>P</minit>
    <lname>Ashworth</lname>
    <job_id>6</job_id>
    <job_lvl>140</job_lvl>
    <pub_id>0877</pub_id>
    <hire_date>1990-09-13T00:00:00.0000000-04:00</hire_date>
  </employee>
  <employee>
    <emp_id>H-B39728F</emp_id>
    <fname>Helen</fname>
    <minit> </minit>
    <lname>Bennett</lname>
    <job_id>12</job_id>
    <job_lvl>35</job_lvl>
    <pub_id>0877</pub_id>
    <hire_date>1989-09-21T00:00:00.0000000-04:00</hire_date>
  </employee>
        .
        .
        .

Here's what the XML schema for this table looks like:

<?xml version="1.0" standalone="yes"?>
<xs:schema id="DataSet1" targetNamespace="http://www.tempuri.org/DataSet1.xsd"
xmlns="http://www.tempuri.org/DataSet1.xsd"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"
attributeFormDefault="qualified" elementFormDefault="qualified">
  <xs:element name="DataSet1" msdata:IsDataSet="true">
    <xs:complexType>
      <xs:choice maxOccurs="unbounded">
        <xs:element name="authors">
          <xs:complexType>
            <xs:sequence>
              <xs:element name="au_id" type="xs:string" />
              <xs:element name="au_lname" type="xs:string" />
              <xs:element name="au_fname" type="xs:string" />
              <xs:element name="phone" type="xs:string" />
              <xs:element name="address" type="xs:string" minOccurs="0" />
              <xs:element name="city" type="xs:string" minOccurs="0" />
              <xs:element name="state" type="xs:string" minOccurs="0" />
              <xs:element name="zip" type="xs:string" minOccurs="0" />
              <xs:element name="contract" type="xs:boolean" />
            </xs:sequence>
          </xs:complexType>
        </xs:element>
        <xs:element name="employee">
          <xs:complexType>
            <xs:sequence>
              <xs:element name="emp_id" type="xs:string" minOccurs="0" />
              <xs:element name="fname" type="xs:string" minOccurs="0" />
              <xs:element name="minit" type="xs:string" minOccurs="0" />
              <xs:element name="lname" type="xs:string" minOccurs="0" />
              <xs:element name="job_id" type="xs:short" minOccurs="0" />
              <xs:element name="job_lvl" type="xs:unsignedByte"
                  minOccurs="0" />
              <xs:element name="pub_id" type="xs:string" minOccurs="0" />
              <xs:element name="hire_date" type="xs:dateTime" minOccurs="0" />
            </xs:sequence>
          </xs:complexType>
        </xs:element>
      </xs:choice>
    </xs:complexType>
    <xs:unique name="Constraint1" msdata:PrimaryKey="true">
      <xs:selector xpath=".//mstns:authors" />
      <xs:field xpath="mstns:au_id" />
    </xs:unique>
  </xs:element>
</xs:schema>

This XML document and XML schema show the actual way that data is transmitted from database to .NET application and back again by using ADO.NET. Listing 20.2 shows the code we've written for this example.

Example 20.2. Button-Handling Code in the `ch20_03` Project (from `Form1.vb` in the `ch20_03` Project)

Public Class Form1
    Inherits System.Windows.Forms.Form
        .
        .
        .
    Private Sub Button1_Click(ByVal sender As System.Object, _
        ByVal e As System.EventArgs) Handles Button1.Click
        DataSet11.Clear()
        OleDbDataAdapter1.Fill(DataSet11)
        DataSet11.WriteXml("data.xml")
        DataSet11.WriteXmlSchema("dataSchema.xml")
    End Sub

    Private Sub Button2_Click(ByVal sender As System.Object, _
        ByVal e As System.EventArgs) Handles Button2.Click
        Dim ds As New DataSet
        ds.ReadXml("data.xml")
        DataGrid1.SetDataBinding(ds, "employee")
    End Sub
End Class

< Back Page 251 of 288 Next >

🔖 Save To Your Account

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.

Privacy Notice

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

Email Address