ASP.NET
  Home arrow ASP.NET arrow Page 4 - Interacting with Databases
ASP Free Forums 
.NET  
ASP  
ASP Code  
ASP.NET  
ASP.NET Code  
BrainDump  
C#  
Code Examples  
Database  
Database Code  
IIS  
Microsoft Access  
MS SQL Server  
Visual Basic.NET  
Windows Scripting  
Windows Security  
XML  
ASP Web Hosting  
ASP.NET Web Hosting 
Mobile Linux 
App Generation ROI 
Windows Web Hosting
 
IBM® developerWorks 
Sun Developer Network 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
ASP.NET

Interacting with Databases
By: McGraw-Hill/Osborne
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 5 stars5 stars5 stars5 stars5 stars / 14
    2006-04-06

    Table of Contents:
  • Interacting with Databases
  • Namespaces and Classes
  • Creating a Database and Tables
  • Were Any Rows Returned?

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Interacting with Databases - Were Any Rows Returned?


    (Page 4 of 4 )

    The question that your application needs to answer after sending a query to a DBMS is whether or not the DBMS found any information that matches your query. The easiest way to answer this question is to examine the HasRows property of the DataReader class.

    The value of the HasRows property determines if any records were returned by the DBMS. It is true if records are returned; otherwise, the value of the HasRows property is false. It is important to remember that the HasRows property does not tell you the number of records that are returned. Instead, it simply states if any are returned.

    Let’s modify the previous examples to include the HasRows property. We’ll begin with the Microsoft SQL Server example.

    <% Import Namespace="System.Data.SqlClient" %>
    <%
      
    Dim custDb As SqlConnection
      
    Dim cmdSelectCustomers As SqlCommand
      
    Dim dtrCustomers As SqlDataReader
      
    custDb = New SqlConnection("Server=localhost;uid=myID;pwd=mypassword;
    database=customer")
      
    custDb.Open()
      
    cmdSelectCustomers = New SqlCommand( "Select custFirstName, custLastName From
    custContact", custDb)
      
    dtrCustomers = cmdSelectCustomers.ExecuteReader()
      
    If dtrCustomers.HasRows Then
         
    While dtrCustomers.Read()
     Response.Write(CStr(dtrCustomers.Item("custFirstName")) & " " & _
                        
    CStr(dtrCustomers.Item("custLastName")))
    Response.Write("<BR>")
         
    End While
       Else
         
    Response.Write("There are no customers.")
      
    End If
      
    dtrCustomers.Close()
      
    custDb.Close()
    %>

    Here’s how to do this with Microsoft Access:

    <% Import Namespace="System.Data.OleDb" %>
    <%
      
    Dim custDb As OleDbConnection
      
    Dim cmdSelectCustomers As OleDbCommand
      
    Dim dtrCustomers As OleDbDataReader
      
    custDb = New OleDbConnection( "PROVIDER=Microsoft.Jet.OLEDB.4.0;Data Source=c:
    ust.mdb")
      
    custDb.Open()
      
    cmdSelectCustomers = New OleDbCommand( "Select custFirstName, custLastName From
    custContact", custDb)
      
    dtrCustomers = cmdSelectCustomers.ExecuteReader()
      
    If dtrCustomers.HasRows Then
         
    While dtrCustomers.Read()
    Response.Write(CStr(dtrCustomers.Item("custFirstName")) & " " & _
                        
    CStr(dtrCustomers.Item("custLastName")))
            
    Response.Write("<BR>")
         
    End While
      
    Else
         
    Response.Write("There are no customers.")
      
    End If
      
    dtrCustomers.Close()
      
    custDb.Close()
    %>

    Retrieving a Specific Row

    It is very common that you’ll need to look for particular information stored in a database such as a customer number. To do this, you’ll need to include a Where clause in your query. The Where clause requires two pieces of information: a search value and the column that contains the search value.

    Let’s say that you want to retrieve the customer number and customer name for customer number 1234. Here’s the query that you’ll need to write:

    Select custNumber, custFirstName, custLastName
    From custContact
    Where custNumber = '1234'

    The Select statement is nearly identical to the query you wrote earlier in this chapter, except we’ve included the custNumber column. Remember that columns that appear in the Select statement are returned by the DBMS.

    The From clause is the same as in other queries in that it tells the DBMS to use the custContact table.

    The Where clause is new to the query. It tells the DBMS to search for 1234 in the custNumber column. Only rows that have 1234 in the custNumber column are returned by the DBMS. There is only one row in our example that has 1234 as a customer number, so only that row is returned.

    Replace the query in the previous examples with this query and run the application to retrieve customer Bob Smith from the DBMS.

    Please check back next week for the continuation of this article.


    DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.

       · This article is an excerpt from the book "ASP.NET 2.0 DeMYSTiFieD," published by...
     

    Buy this book now. This article is excerpted from chapter 10 of ASP.NET 2.0 DeMYSTiFieD, written by Jim Keogh (McGraw-Hill/Osborne; ISBN: 0072261412). Check it out today at your favorite bookstore. Buy this book now.

    ASP.NET ARTICLES

    - Developing a Mini ASP.NET AJAX Server Centri...
    - Disadvantages of the ASP.NET MVC Framework
    - Advantages of the ASP.NET MVC Approach
    - ASP.NET Web Forms Weaknesses
    - ASP.NET Web Forms Meets ASP.NET MVC
    - Source Code for Saving and Retrieving Data w...
    - Using GridView to Save and Retrieve Data wit...
    - Handling Dynamic Images in ASP.NET 3.5 AJAX ...
    - Retrieving Data with AJAX and the GridView C...
    - Playing with Images in ASP.NET 3.5 AJAX Appl...
    - Saving and Retrieving Data with AJAX
    - Enhancing PHP Via the ASP.NET AJAX Framework...
    - Enhancing PHP Programming with the ASP.NET A...
    - Classes and ASP.NET AJAX
    - Using ASP.NET AJAX

     
    Best Practices for Windows Vista Migration Presentation
    Dell and Microsoft recently held a series of face-to-face seminars entitled, &qu....

     
    Creating a Culture for Code Reuse
    If you oversee development teams you know that like it or not proprietary and ex....

     
    Keys to Web Application Acceleration: Advances in Delivery Systems
    Accelerate Web apps by up to 5x. Ensure significantly faster access to the Web a....

     
    Optimizing Application Monitoring
    Tired of finding out from your customers that you're offline? This white paper e....

     
    Solaris to Solaris Migration -- Migrating applications from Sun SPARC to Dell PowerEdge R900
    This comprehensive Migration Guide reviews the approach that Principled Technolo....

     




    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 3 hosted by Hostway
    Stay green...Green IT