OdbcCommand.ExecuteReader Method (CommandBehavior)


The .NET API Reference documentation has a new home. Visit the .NET API Browser on docs.microsoft.com to see the new experience.

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

Namespace:   System.Data.Odbc
Assembly:  System.Data (in System.Data.dll)

Public Function ExecuteReader (
	behavior As CommandBehavior
) As OdbcDataReader


Type: System.Data.CommandBehavior

One of the System.Data.CommandBehavior values.

Return Value

Type: System.Data.Odbc.OdbcDataReader

An OdbcDataReader object.

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.


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.

.NET Framework
Available since 1.1
Return to top