Create a simple data application by using ADO.NET

 

For the latest documentation on Visual Studio 2017, see Create a simple data application by using ADO.NET on docs.microsoft.com. When you create an application that manipulates data in a database, you perform basic tasks such defining connection strings, inserting data, and running stored procedures. By following this topic, you can discover how to interact with a database from within a simple Windows Forms "forms over data" application by using Visual C# or Visual Basic and ADO.NET. All .NET data technologies—including datasets, LINQ to SQL, and Entity Framework—ultimately perform steps that are very similar to those shown in this article.

This article demonstrates a simple way to get data out of a database in a very fast manner. If your application needs to modify data in non-trivial ways and update the database, you should consider using Entity Framework and using data binding to automatically sync user interface controls to changes in the underlying data.

System_CAPS_ICON_important.jpg Important

To keep the code simple, it doesn’t include production-ready exception handling.

In this topic

To create the application, you'll need:

  • Visual Studio Community Edition.

  • SQL Server Express LocalDB.

  • The small sample database that you create by following the steps in Create a SQL database by using a script.

  • The connection string for the database after you set it up. You can find this value by opening SQL Server Object Explorer, opening the shortcut menu for the database, selecting Properties, and then scrolling to the ConnectionString property.

This topic assumes that you're familiar with the basic functionality of the Visual Studio IDE and can create a Windows Forms application, add forms to that project, put buttons and other controls on those forms, set properties of those controls, and code simple events. If you aren't comfortable with these tasks, we suggest that you complete the Getting Started with Visual C# and Visual Basic before you start this topic.

The sample database for this walkthrough consists of the Customer and Orders tables. The tables contain no data initially, but you’ll add data when you run the application that you'll create. The database also has five simple stored procedures. Create a SQL database by using a script contains a Transact-SQL script that creates the tables, the primary and foreign keys, the constraints, and the stored procedures.

  1. Create a project for a Windows Forms application, and then name it SimpleDataApp.

    Visual Studio creates the project and several files, including an empty Windows form that's named Form1.

  2. Add two Windows forms to your project so that it has three forms, and then give them the following names:

    • Navigation

    • NewCustomer

    • FillOrCancel

  3. For each form, add the text boxes, buttons, and other controls that appear in the following illustrations. For each control, set the properties that the tables describe.

    System_CAPS_ICON_note.jpg Note

    The group box and the label controls add clarity but aren't used in the code.

Navigation form

Navigation dialog box

Controls for the Navigation formProperties
ButtonName = btnGoToAdd
ButtonName = btnGoToFillOrCancel
ButtonName = btnExit

NewCustomer form

Add  a new customer and place an order

Controls for the NewCustomer formProperties
TextBoxName = txtCustomerName
TextBoxName = txtCustomerID

Readonly = True
ButtonName = btnCreateAccount
NumericUpdownDecimalPlaces = 0

Maximum = 5000

Name = numOrderAmount
DateTimePickerFormat = Short

Name = dtpOrderDate
ButtonName = btnPlaceOrder
ButtonName = btnAddAnotherAccount
ButtonName = btnAddFinish

FillOrCancel form

fill or cancel orders

Controls for the FillOrCancel formProperties
TextBoxName = txtOrderID
ButtonName = btnFindByOrderID
DateTimePickerFormat = Short

Name = dtpFillDate
DataGridViewName = dgvCustomerOrders

Readonly = True

RowHeadersVisible = False
ButtonName = btnCancelOrder
ButtonName = btnFillOrder
ButtonName = btnFinishUpdates

When your application tries to open a connection to the database, your application must have access to the connection string. To avoid entering the string manually on each form, store the string in the App config file in your project, and create a method that returns the string when the method is called from any form in your application.

You can find the connection string in SQL Server Object Explorer by right-clicking the database, selecting Properties, and then finding the ConnectionString property. Use Ctrl+A to select the string.

  1. In Solution Explorer, select the Properties node under the project, and then select Settings.settings.

  2. In the Name column, enter connString.

  3. In the Type list, select (Connection String).

  4. In the Scope list, select Application.

  5. In the Value column, enter your connection string (without any outside quotes), and then save your changes.

System_CAPS_ICON_note.jpg Note

In a real application, you should store the connection string securely, as described in Connection Strings and Configuration Files.

  1. On the menu bar, select Project > Add Reference, and then add a reference to System.Configuration.dll.

  2. On the menu bar, select Project > Add Class to add a class file to your project, and then name the file Utility.

    Visual Studio creates the file and displays it in Solution Explorer.

  3. In the Utility file, replace the placeholder code with the following code. Notice the numbered comments (prefixed with Util-) that identify sections of the code. The table that follows the code calls out key points.

    using System;  
    using System.Collections.Generic;  
    using System.Linq;  
    using System.Text;  
    using System.Threading.Tasks;  
    //Util-1 More namespaces.  
    using System.Configuration;   
    
    namespace SimpleDataApp  
    {  
        internal class Utility  
        {  
    
            //Get the connection string from App config file.  
            internal static string GetConnectionString()  
            {  
                //Util-2 Assume failure.  
                string returnValue = null;  
    
                //Util-3 Look for the name in the connectionStrings section.  
                ConnectionStringSettings settings =  
                ConfigurationManager.ConnectionStrings["SimpleDataApp.Properties.Settings.connString"];  
    
                //If found, return the connection string.  
                if (settings != null)  
                    returnValue = settings.ConnectionString;  
    
                return returnValue;  
            }  
        }  
    }  
    
    
    CommentDescription
    Util-1Add the System.Configuration namespace.
    Util-2Define a variable, returnValue, and initialize it to null (C#) or Nothing (Visual Basic).
    Util-3Even though you entered connString as the name of the connection string in the Properties window, you must specify "SimpleDataApp.Properties.Settings.connString" (C#) or "SimpleDataApp.My.MySettings.connString" (Visual Basic) in the code.

This section contains brief overviews of what each form does and shows the code that creates the forms. Numbered comments identify sections of the code.

Navigation form

The Navigation form opens when you run the application. The Add an account button opens the NewCustomer form. The Fill or cancel orders button opens the FillOrCancel form. The Exit button closes the application.

Make the Navigation form the startup form

If you're using C#, in Solution Explorer, open Program.cs, and then change the Application.Run line to this: Application.Run(new Navigation());

If you're using Visual Basic, in Solution Explorer, open the Properties window, select the Application tab, and then select SimpleDataApp.Navigation in the Startup form list.

Create event handlers

Double-click the three buttons on the form to create empty event-handler methods.

Create code for Navigation

In the Navigation form, replace the existing code with the following code.

using System;  
using System.Collections.Generic;  
using System.ComponentModel;  
using System.Data;  
using System.Drawing;  
using System.Linq;  
using System.Text;  
using System.Threading.Tasks;  
using System.Windows.Forms;  
  
namespace SimpleDataApp  
{  
    public partial class Navigation : Form  
    {  
        public Navigation()  
        {  
            InitializeComponent();  
        }  
  
        //Open the NewCustomer form as a dialog box, which will return focus to the calling form when it closes.  
        private void btnGoToAdd_Click(object sender, EventArgs e)  
        {  
            Form frm = new NewCustomer();  
            frm.Show();  
        }  
  
        //Open the FillorCancel form as a dialog box.  
        private void btnGoToFillOrCancel_Click(object sender, EventArgs e)  
        {  
            Form frm = new FillOrCancel();  
            frm.ShowDialog();  
        }  
  
        //Close the application, not just the Navigation form.  
        private void btnExit_Click(object sender, EventArgs e)  
        {  
            this.Close();  
        }  
    }  
}  

NewCustomer form

When you enter a customer name and then select the Create Account button, the NewCustomer form creates a customer account, and SQL Server returns an IDENTITY value as the new account number. You then place an order for the new account by specifying an amount and an order date and selecting the Place Order button.

Create event handlers

Create an empty Click event handler for each button on the form.

Create code for NewCustomer

Add the following code to the NewCustomer form. Step through each code block by using the numbered comments and the table after the code.

using System;  
using System.Collections.Generic;  
using System.ComponentModel;  
using System.Data;  
using System.Drawing;  
using System.Linq;  
using System.Text;  
using System.Threading.Tasks;  
using System.Windows.Forms;  
//NC-1 More namespaces.  
using System.Data.SqlClient;  
using System.Configuration;  
  
namespace SimpleDataApp  
{  
    public partial class NewCustomer : Form  
    {  
        //NC-2 Storage for IDENTITY values returned from database.  
        private int parsedCustomerID;  
        private int orderID;  
  
        //NC-3 Specify a connection string.  
        string connstr = SimpleDataApp.Utility.GetConnectionString();  
  
        public NewCustomer()  
        {  
            InitializeComponent();  
        }  
  
        //NC-4 Create account.  
        private void btnCreateAccount_Click(object sender, EventArgs e)  
        {  
            //NC-5 Set up and run stored procedure only if Customer Name is present.  
            if (isCustomerName())  
            {  
  
                //NC-6 Create the connection.  
                SqlConnection conn = new SqlConnection(connstr);  
  
                //NC-7 Create a SqlCommand, and identify it as a stored procedure.  
                SqlCommand cmdNewCustomer = new SqlCommand("Sales.uspNewCustomer", conn);  
                cmdNewCustomer.CommandType = CommandType.StoredProcedure;  
  
                //NC-8 Add input parameter from the stored procedure and specify what to use as its value.  
                cmdNewCustomer.Parameters.Add(new SqlParameter("@CustomerName", SqlDbType.NVarChar, 40));  
                cmdNewCustomer.Parameters["@CustomerName"].Value = txtCustomerName.Text;  
  
                //NC-9 Add output parameter.  
                cmdNewCustomer.Parameters.Add(new SqlParameter("@CustomerID", SqlDbType.Int));  
                cmdNewCustomer.Parameters["@CustomerID"].Direction = ParameterDirection.Output;  
  
                //NC-10 try-catch-finally  
                try  
                {  
                    //NC-11 Open the connection.  
                    conn.Open();  
  
                    //NC-12 Run the stored procedure.  
                    cmdNewCustomer.ExecuteNonQuery();  
  
                    //NC-13 Customer ID is an IDENTITY value from the database.   
                    this.parsedCustomerID = (int)cmdNewCustomer.Parameters["@CustomerID"].Value;  
                    this.txtCustomerID.Text = Convert.ToString(parsedCustomerID);  
  
                }  
                catch  
                {  
                    //NC-14 A simple catch.  
  
                    MessageBox.Show("Customer ID was not returned. Account could not be created.");  
                }  
                finally  
                {  
                    //NC-15 Close the connection.  
                    conn.Close();  
                }  
            }  
        }  
  
        //NC-16 Verify that Customer Name is present.  
        private bool isCustomerName()  
        {  
            if (txtCustomerName.Text == "")  
            {  
                MessageBox.Show("Please enter a name.");  
                return false;  
            }  
            else  
            {  
                return true;  
            }  
        }  
  
        //NC-17 Place order.  
        private void btnPlaceOrder_Click(object sender, EventArgs e)  
        {  
            //NC-18 Set up and run stored procedure only if required input is present.  
            if (isPlaceOrderReady())  
            {  
                // Create the connection.  
                SqlConnection conn = new SqlConnection(connstr);  
  
                //NC-19 Create SqlCommand and identify it as a stored procedure.  
                SqlCommand cmdNewOrder = new SqlCommand("Sales.uspPlaceNewOrder", conn);  
                cmdNewOrder.CommandType = CommandType.StoredProcedure;  
  
                //NC-20 @CustomerID, which was an output parameter from uspNewCustomer.  
                cmdNewOrder.Parameters.Add(new SqlParameter("@CustomerID", SqlDbType.Int));  
                cmdNewOrder.Parameters["@CustomerID"].Value = this.parsedCustomerID;  
  
                //NC-21 @OrderDate.  
                cmdNewOrder.Parameters.Add(new SqlParameter("@OrderDate", SqlDbType.DateTime, 8));  
                cmdNewOrder.Parameters["@OrderDate"].Value = dtpOrderDate.Value;  
  
                //NC-22 @Amount.  
                cmdNewOrder.Parameters.Add(new SqlParameter("@Amount", SqlDbType.Int));  
                cmdNewOrder.Parameters["@Amount"].Value = numOrderAmount.Value;  
  
                //NC-23 @Status. For a new order, the status is always O (open).  
                cmdNewOrder.Parameters.Add(new SqlParameter("@Status", SqlDbType.Char, 1));  
                cmdNewOrder.Parameters["@Status"].Value = "O";  
  
                //NC-24 Add return value for stored procedure, which is orderID.  
                cmdNewOrder.Parameters.Add(new SqlParameter("@RC", SqlDbType.Int));  
                cmdNewOrder.Parameters["@RC"].Direction = ParameterDirection.ReturnValue;  
  
                //try-catch-finally  
                try  
                {  
                    //Open connection.  
                    conn.Open();  
  
                    //Run the stored procedure.  
                    cmdNewOrder.ExecuteNonQuery();  
  
                    //NC-25 Display the order number.  
                    this.orderID = (int)cmdNewOrder.Parameters["@RC"].Value;  
                    MessageBox.Show("Order number " + this.orderID + " has been submitted.");  
                }  
                catch  
                {  
                    //A simple catch.  
                    MessageBox.Show("Order could not be placed.");  
                }  
                finally  
                {  
                    //Close connection.  
                    conn.Close();  
                }  
            }  
        }  
  
        //NC-26 Verify that order data is ready.  
        private bool isPlaceOrderReady()  
        {  
            // Verify that CustomerID is present.  
            if (txtCustomerID.Text == "")  
            {  
                MessageBox.Show("Please create customer account before placing order.");  
                return false;  
            }  
  
            // Verify that Amount isn't 0.   
            else if ((numOrderAmount.Value < 1))  
            {  
                MessageBox.Show("Please specify an order amount.");  
                return false;  
            }  
            else  
            {  
                // Order can be submitted.  
                return true;  
            }  
        }  
  
        //NC-27 Reset the form for another new account.  
        private void btnAddAnotherAccount_Click(object sender, EventArgs e)  
        {  
            this.ClearForm();  
        }  
  
        //NC-28 Clear values from controls.  
        private void ClearForm()  
        {  
            txtCustomerName.Clear();  
            txtCustomerID.Clear();  
            dtpOrderDate.Value = DateTime.Now;  
            numOrderAmount.Value = 0;  
            this.parsedCustomerID = 0;  
        }  
  
        //NC-29 Close the form.  
        private void btnAddFinish_Click(object sender, EventArgs e)  
        {  
            this.Close();  
        }  
  
    }  
}  
  

CommentDescription
NC-1Add System.Data.SqlClient and System.Configuration to the list of namespaces.
NC-2Declare the parsedCustomerID and orderID variables, which you'll use later.
NC-3Call the GetConnectionString method to get the connection string from the App config file, and store the value in the connstr string variable.
NC-4Add code to the Click event handler for the btnCreateAccount button.
NC-5Wrap the call to isCustomerName around the Click event code so that uspNewCustomer runs only if a customer name is present.
NC-6Create a SqlConnection object (conn), and pass in the connection string in connstr.
NC-7Create a SqlCommand object, cmdNewCustomer.

- Specify Sales.uspNewCustomer as the stored procedure to run.
- Use the CommandType property to specify that the command is a stored procedure.
NC-8Add the @CustomerName input parameter from the stored procedure.

- Add the parameter to the Parameters collection.
- Use the SqlDbType enumeration to specify the parameter type as nvarchar(40).
- Specify txtCustomerName.Text as the source.
NC-9Add the output parameter from the stored procedure.

- Add the parameter to the Parameters collection.
- Use ParameterDirection.Output to identify the parameter as output.
NC-10Add a Try-Catch-Finally block to open the connection, run the stored procedure, handle exceptions, and then close the connection.
NC-11Open the connection (conn) that you created at NC-6.
NC-12Use the ExecuteNonQuery method for cmdNewCustomer to run the Sales.uspNewCustomer stored procedure. This stored procedure runs an INSERT statement, not a query.
NC-13The @CustomerID value is returned as an IDENTITY value from the database. Because it's an integer, you'll have to convert it to a string to display it in the Customer ID text box.

- You declared parsedCustomerID at NC-2.
- Store the @CustomerID value in parsedCustomerID for later use.
- Convert the returned customer ID to a string, and insert it into txtCustomerID.Text.
NC-14For this sample, add a simple (not production-quality) catch clause.
NC-15Always close a connection after you finish using it, so that it can be released to the connection pool. See SQL Server Connection Pooling (ADO.NET).
NC-16Define a method to verify that a customer name is present.

- If the text box is empty, display a message and return false, because a name is required to create the account.
- If the text box isn't empty, return true.
NC-17Add code to the Click event handler for the btnPlaceOrder button.
NC-18Wrap the call to isPlaceOrderReady around the btnPlaceOrder_Click event code so that uspPlaceNewOrder doesn't run if required input isn't present.
NC-19 through NC-25These sections of code resemble the code that you added for the btnCreateAccount_Click event handler.

- NC-19. Create the SqlCommand object, cmdNewOrder, and specify Sales.uspPlaceOrder as the stored procedure.
- NC-20 through NC-23 are the input parameters for the stored procedure.
- NC-24. @RC will contain a return value that's the generated order ID from the database. This parameter's direction is specified as ReturnValue.
- NC-25. Store the value of order ID in the orderID variable that you declared at NC-2, and display the value in a message box.
NC-26Define a method to verify that a customer ID exists and that an amount has been specified in numOrderAmount.
NC-27Call the ClearForm method in the btnAddAnotherAccount Click event handler.
NC-28Create the ClearForm method to clear values from the form if you want to add another customer.
NC29Close the NewCustomer form, and return focus to the Navigation form.

FillOrCancel form

The FillorCancel form runs a query to return an order when you enter an order ID and select the Find Order button. The returned row appears in a read-only data grid. You can mark the order as canceled (X) if you select the Cancel Order button, or you can mark the order as filled (F) if you select the Fill Order button. If you select the Find Order button again, the updated row appears.

Create event handlers

Create empty Click event handlers for the four buttons on the form.

Create code for FillOrCancel

Add the following code to the FillOrCancel form. Step through the code blocks by using the numbered comments and the table that follows the code.

using System;  
using System.Collections.Generic;  
using System.ComponentModel;  
using System.Data;  
using System.Drawing;  
using System.Linq;  
using System.Text;  
using System.Threading.Tasks;  
using System.Windows.Forms;  
//FC-1 More namespaces.  
using System.Text.RegularExpressions;  
using System.Data.SqlClient;  
using System.Configuration;  
  
namespace SimpleDataApp  
{  
    public partial class FillOrCancel : Form  
    {  
        //FC-2 Storage for OrderID.  
        private int parsedOrderID;  
  
        //FC-3 Specify a connection string.  
        string connstr = SimpleDataApp.Utility.GetConnectionString();  
  
        public FillOrCancel()  
        {  
            InitializeComponent();  
        }  
  
        //FC-4 Find an order.  
        private void btnFindByOrderID_Click(object sender, EventArgs e)  
        {  
            //FC-5 Prepare the connection and the command.  
            if (isOrderID())  
            {  
                //Create the connection.  
                SqlConnection conn = new SqlConnection(connstr);  
  
                //Define a query string that has a parameter for orderID.  
                string sql = "select * from Sales.Orders where orderID = @orderID";  
  
                //Create a SqlCommand object.  
                SqlCommand cmdOrderID = new SqlCommand(sql, conn);  
  
                //Define the @orderID parameter and its value.  
                cmdOrderID.Parameters.Add(new SqlParameter("@orderID", SqlDbType.Int));  
                cmdOrderID.Parameters["@orderID"].Value = parsedOrderID;  
  
                //try-catch-finally  
                try  
                {  
                    //FC-6 Run the command and display the results.  
                    //Open the connection.  
                    conn.Open();  
  
                    //Run the command by using SqlDataReader.  
                    SqlDataReader rdr = cmdOrderID.ExecuteReader();  
  
                    //Create a data table to hold the retrieved data.  
                    DataTable dataTable = new DataTable();  
  
                    //Load the data from SqlDataReader into the data table.  
                    dataTable.Load(rdr);  
  
                    //Display the data from the data table in the data grid view.  
                    this.dgvCustomerOrders.DataSource = dataTable;  
  
                    //Close the SqlDataReader.  
                    rdr.Close();  
                }  
                catch  
                {  
                    //A simple catch.  
                    MessageBox.Show("The requested order could not be loaded into the form.");  
                }  
                finally  
                {  
                    //Close the connection.  
                    conn.Close();  
                }  
            }  
        }  
  
        //FC-7 Cancel an order.  
        private void btnCancelOrder_Click(object sender, EventArgs e)  
        {  
            //Set up and run stored procedure only if OrderID is ready.  
            if (isOrderID())  
            {  
                //Create the connection.  
                SqlConnection conn = new SqlConnection(connstr);  
  
                // Create command and identify it as a stored procedure.  
                SqlCommand cmdCancelOrder = new SqlCommand("Sales.uspCancelOrder", conn);  
                cmdCancelOrder.CommandType = CommandType.StoredProcedure;  
  
                cmdCancelOrder.Parameters.Add(new SqlParameter("@orderID", SqlDbType.Int));  
                cmdCancelOrder.Parameters["@orderID"].Value = parsedOrderID;  
  
                // try-catch-finally  
                try  
                {  
                    // Open the connection.  
                    conn.Open();  
  
                    // Run the cmdCancelOrder command.  
                    cmdCancelOrder.ExecuteNonQuery();  
                }  
                // A simple catch.  
                catch  
                {  
                    MessageBox.Show("The cancel operation was not completed.");  
                }  
                finally  
                {  
                    //Close connection.  
                    conn.Close();  
                }  
            }  
        }  
  
        //FC-8 Fill an order.  
        private void btnFillOrder_Click(object sender, EventArgs e)  
        {  
            //Set up and run stored procedure only if OrderID is ready.  
            if (isOrderID())  
            {  
                //Create the connection.  
                SqlConnection conn = new SqlConnection(connstr);  
  
                //Create command and identify it as a stored procedure.  
                SqlCommand cmdFillOrder = new SqlCommand("Sales.uspFillOrder", conn);  
                cmdFillOrder.CommandType = CommandType.StoredProcedure;  
  
                // Add input parameter from the stored procedure.  
                cmdFillOrder.Parameters.Add(new SqlParameter("@orderID", SqlDbType.Int));  
                cmdFillOrder.Parameters["@orderID"].Value = parsedOrderID;  
  
                //Add the second input parameter.  
                cmdFillOrder.Parameters.Add(new SqlParameter("@FilledDate", SqlDbType.DateTime, 8));  
                cmdFillOrder.Parameters["@FilledDate"].Value = dtpFillDate.Value;  
  
                //try-catch-finally  
                try  
                {  
                    //Open the connection.  
                    conn.Open();  
  
                    //Run the cmdFillOrder command.  
                    cmdFillOrder.ExecuteNonQuery();  
                }  
                catch  
                {  
                    //A simple catch.  
                    MessageBox.Show("The fill operation was not completed.");  
                }  
                finally  
                {  
                    //Close the connection.  
                    conn.Close();  
                }  
            }  
        }  
  
        //FC-9 Verify that OrderID is ready.  
        private bool isOrderID()  
        {  
  
            //Check for input in the Order ID text box.  
            if (txtOrderID.Text == "")  
            {  
                MessageBox.Show("Please specify the Order ID.");  
                return false;  
            }  
  
            // Check for characters other than integers.  
            else if (Regex.IsMatch(txtOrderID.Text, @"^\D*$"))  
            {  
               //Show message and clear input.  
                MessageBox.Show("Please specify integers only.");  
                txtOrderID.Clear();  
                return false;  
            }  
            else  
            {  
                //Convert the text in the text box to an integer to send to the database.  
                parsedOrderID = Int32.Parse(txtOrderID.Text);  
                return true;  
            }  
        }  
  
        //Close the form.  
        private void btnFinishUpdates_Click(object sender, EventArgs e)  
        {  
            this.Close();  
        }  
    }  
}  

CommentDescription
FC-1Add System.Data.SqlClient, System.Configuration, and System.Text.RegularExpressions to the list of namespaces.
FC-2Declare the parsedOrderID variable.
FC-3Call the GetConnectionString method to get the connection string from the App config file, and store the value in the connstr string variable.
FC-4Add code to the Click event handler for btnFindOrderByID.
FC-5These tasks are required before you try to run an SQL statement or a stored procedure.

- Create a SqlConnection object.
- Define the SQL statement or specify the name of the stored procedure. (In this case, you'll run a SELECT statement.)
- Create a SqlCommand object.
- Define any parameters for the SQL statement or stored procedure.
FC-6This code uses SqlDataReader and DataTable to retrieve and display the query result.

- Open the connection.
- Create a SqlDataReader object, rdr, by running the ExecuteReader method for cmdOrderID.
- Create a DataTable object to hold the retrieved data.
- Load the data from the SqlDataReader object into the DataTable object.
- Display the data in the data grid view by specifying DataTable as DataSource for the data grid view.
- Close SqlDataReader.
FC-7Add code to the Click event handler for btnCancelOrder. This code runs the Sales.uspCancelOrder stored procedure.
FC-8Add code to the Click event handler for btnFillOrder. This code runs the Sales.uspFillOrder stored procedure.
FC-9Create a method to verify that OrderID is ready to submit as a parameter to the SqlCommand object.

- Make sure that an ID has been entered in txtOrderID.
- Use Regex.IsMatch to define a simple check for non-integer characters.
- You declared the parsedOrderID variable at FC-2.
- If the input is valid, convert the text to an integer, and store the value in the parsedOrderID variable.
- Wrap the isOrderID method around the btnFindByOrderID, btnCancelOrder, and btnFillOrder Click event handlers.

Select the F5 key to build and test your application after you code each Click event handler, and then after you finish coding.

Show: