Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
CommandType Property

OdbcCommand::CommandType Property

Gets or sets a value that indicates how the CommandText property is interpreted.

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

public:
virtual property CommandType CommandType {
	CommandType get () override;
	void set (CommandType value) override;
}

Property Value

Type: System.Data::CommandType
One of the CommandType values. The default is Text.

Implements

IDbCommand::CommandType

ExceptionCondition
ArgumentException

The value was not a valid CommandType.

When the CommandType property is set to StoredProcedure, you should set the CommandText property to the full ODBC call syntax. The command then executes this stored procedure when you call one of the Execute methods (for example, ExecuteReader or ExecuteNonQuery).

The Connection, CommandType and CommandText properties cannot be set if the current connection is performing an execute or fetch operation.

The .NET Framework Data Provider for ODBC does not support passing named parameters to an SQL statement or to a stored procedure called by an OdbcCommand. In either of these cases, use the question mark (?) placeholder. For example:

SELECT * FROM Customers WHERE CustomerID = ?

The order in which OdbcParameter objects are added to the OdbcParameterCollection must directly correspond to the position of the question mark placeholder for the parameter.

NoteNote

The .NET Framework Data Provider for ODBC does not support the CommandType setting of TableDirect.

.NET Framework

Supported in: 4.6, 4.5, 4, 3.5, 3.0, 2.0, 1.1

.NET Framework Client Profile

Supported in: 4, 3.5 SP1

Reference

[!:System.Data.Odbc.OdbcCommand.UpdatedRowSource]

Other Resources

Show:
© 2015 Microsoft