Microsoft KB Archive/317150

= HOW TO: Reuse the SqlCommand and OleDbCommand Objects in Visual Basic .NET =

Article ID: 317150

Article Last Modified on 9/3/2003

-

APPLIES TO


 * Microsoft ADO.NET 1.1
 * Microsoft ADO.NET 1.0
 * Microsoft Visual Basic .NET 2003 Standard Edition
 * Microsoft Visual Basic .NET 2002 Standard Edition

-



This article was previously published under Q317150



For a Microsoft Visual C# .NET version of this article, see 317559.

This article refers to the following Microsoft .NET Framework Class Library namespaces:
 * System.Data
 * System.Data.SqlClient

IN THIS TASK
SUMMARY
 * Description of the Technique
 * Steps to Reuse the SqlCommand Object
 * Troubleshooting

REFERENCES



SUMMARY
This step-by-step article describes how to reuse the SqlCommand object in your Visual Basic .NET code.

back to the top

Description of the Technique
You can reuse Command objects (SqlCommand or OleDbCommand) in code. That is, you can create one Command object and then run different commands on that object.

Commands are issued against databases to take actions against data stores. Commands include any statement that can be issued against a database. You can use the OleDbCommand or the SqlCommand class to get a command for your data store.

In Microsoft ActiveX Data Objects (ADO), you can issue commands through the Command, the Connection, or the Recordset object. In Microsoft ADO.NET, only the Command objects (SqlCommand or OleDbCommand) run commands.

back to the top

Steps to Reuse a SqlCommand Object
 Create a new Windows application in Visual Basic .NET as follows:  Start Microsoft Visual Studio .NET. On the File menu, point to New, and then click Project. In the New Project dialog box, click Visual Basic Projects under Project Types, and then click Windows Application under Templates. Form1 is added to the project by default.  Make sure that your project contains a reference to the System.Data namespace. If it does not, add a reference to this namespace. Drag a Button control from the toolbox to Form1. Change the Name property of the button to btnTest .</li>  Use the Imports statement on the System and the System.Data namespaces so that you are not required to qualify declarations in those namespaces later in your code. Add the following code to the &quot;General Declarations&quot; section of Form1: Imports System Imports System.Data Imports System.Data.SqlClient </li>  Copy and paste the following code in the btnTest_Click event: Try Dim myConnString As String = _ &quot;User ID=myUID;password=myPWD;Initial Catalog=pubs;Data Source=mySQLServer&quot; Dim mySelectQuery As String = &quot;SELECT * FROM Titles&quot; Dim myConnection As New SqlConnection(myConnString) Dim myCommand As New SqlCommand(mySelectQuery, myConnection) myConnection.Open Dim myReader As SqlDataReader = myCommand.ExecuteReader While myReader.Read 'Process data. End While myReader.Close 'Close the reader.

myCommand.CommandText = &quot;SELECT * FROM Sales&quot; Dim myReader1 As SqlDataReader = myCommand.ExecuteReader While myReader1.Read 'Process data. End While myReader1.Close 'Close the reader.

Dim myInsertQuery As String = &quot;INSERT INTO Employee &quot; & _ &quot;(emp_id, fname, minit, lname, job_id, job_lvl, pub_id, hire_date)&quot; & _ &quot;VALUES ('MSD12923F', 'JP', 'W', 'Mackenzie', &quot; & _         &quot;10, 82,'0877','2001-01-01')&quot; myCommand.CommandText = myInsertQuery myCommand.ExecuteNonQuery

'You can use the command any number of times.

myConnection.Close Catch ex As Exception MessageBox.Show(ex.ToString) End Try </li> Modify the connection string (myConnString) as appropriate for your environment.</li> Save your project. On the Debug menu, click Start to run your project.</li></ol>

back to the top

Troubleshooting
<ul> While the SqlDataReader object is in use, the associated SqlConnection object serves the SqlDataReader, and you cannot perform any other operations on the SqlConnection object other than to close it. This is true until you call the Close method of the SqlDataReader object. This means, for example, that you cannot retrieve output parameters until after you call Close.For additional information about how to handle output parameters, click the article number below to view the article in the Microsoft Knowledge Base:

308051 PRB: Output Parameters Are Not Returned When You Run an ADO.NET Command in Visual Basic .NET

</li> If the method that runs a SqlCommand generates a SqlException exception, the SqlConnection remains open if the severity level is 19 or less. If the severity level is 20 or greater, the server usually closes the SqlConnection. However, you can reopen the connection and continue.</li></ul>

back to the top

<div class="references_section">