OdbcCommand.ExecuteReader Method

Definition

Namespace:

System.Data.Odbc

Assembly:

System.Data.Odbc.dll

Package:

System.Data.Odbc v9.0.0-rc.2.24473.5

Sends the CommandText to the Connection and builds an OdbcDataReader.

Overloads

ExecuteReader()	Sends the CommandText to the Connection and builds an OdbcDataReader.
ExecuteReader(CommandBehavior)	Sends the CommandText to the Connection, and builds an OdbcDataReader using one of the CommandBehavior values.

ExecuteReader()

Source:

OdbcCommand.cs

Sends the CommandText to the Connection and builds an OdbcDataReader.

public:
 System::Data::Odbc::OdbcDataReader ^ ExecuteReader();

public System.Data.Odbc.OdbcDataReader ExecuteReader ();

override this.ExecuteReader : unit -> System.Data.Odbc.OdbcDataReader

Public Function ExecuteReader () As OdbcDataReader

Returns

OdbcDataReader

An OdbcDataReader object.

Remarks

You should set the CommandText property to the full ODBC call syntax for stored procedures. The command executes this stored procedure when you call ExecuteReader.

While the OdbcDataReader is used, the associated OdbcConnection is busy serving the OdbcDataReader. While in this state, no other operations can be performed on the OdbcConnection other than closing it. This is the case until the Close method of the OdbcDataReader is called.

See also

• Executing a Command

ExecuteReader(CommandBehavior)

Source:

OdbcCommand.cs

Sends the CommandText to the Connection, and builds an OdbcDataReader using one of the CommandBehavior values.

public:
 System::Data::Odbc::OdbcDataReader ^ ExecuteReader(System::Data::CommandBehavior behavior);

public System.Data.Odbc.OdbcDataReader ExecuteReader (System.Data.CommandBehavior behavior);

override this.ExecuteReader : System.Data.CommandBehavior -> System.Data.Odbc.OdbcDataReader

Public Function ExecuteReader (behavior As CommandBehavior) As OdbcDataReader

Parameters

behavior

CommandBehavior

One of the System.Data.CommandBehavior values.

Returns

OdbcDataReader

An OdbcDataReader object.

Remarks

If you expect your SQL statement to return only a single row, specifying SingleRow as the CommandBehavior value may improve application performance.

You should set the CommandText property to the full ODBC call syntax for stored procedures. The command executes this stored procedure when you call ExecuteReader.

The OdbcDataReader supports a special mode that enables large binary values to be read efficiently. For more information, see the SequentialAccess setting for CommandBehavior.

Note

The SequentialAccess value of CommandBehavior is not a limiting setting; it just means that you will have at least sequential access to the OdbcDataReader. For example, when you use the SQL Server ODBC Driver in SequentialAccess mode, you can still move to the first column of an OdbcDataReader row after having read through all the other columns sequentially.

While the OdbcDataReader is used, the associated OdbcConnection is busy serving the OdbcDataReader. While in this state, no other operations can be performed on the OdbcConnection other than closing it. This is the case until you call the OdbcDataReader.Close method. If the OdbcDataReader is created with CommandBehavior set to CloseConnection, closing the OdbcDataReader closes the connection automatically.

See also

• Executing a Command