DataGrid and SQL Server view

[Matt]

Hi,

I'm trying to fill an ASP.NET DataGrid from a SQL-Server View. Note
that this is a View and not a Stored Procedure.

If i write the SQL instructions directly in the code, or if i use a
stored procedure, it works great. But if the same SQL instructions are
in a view, it won't work. Here it goes :


public IDataReader SomeFunction()
{
SqlCommand ObjCmd = new SqlCommand();

ObjCmd.Connection = m_ObjCon;
ObjCmd.CommandText = "[Sales by Category]";
ObjCmd.CommandType = CommandType.StoredProcedure;

return ObjCmd.ExecuteReader();
}


It gives me an error, "The request for procedure 'Sales by Category'
failed because 'Sales by Category' is a view object."

My question is, is it possible to use a view instead of a stored
procedure in this context? I'm a little confused about the difference
between both. Thanks for help!

Matt

[news.microsoft.com]

Hi Matt,

From the perspective of ADO.Net code running in your C# program, a "View" in
SQL Server 2000 is the equivalent of a table. You'll need to write a T-SQL
query in your C# code, or call a stored proc that utilizes the view.

Example: "SELECT * FROM [MyView] a WHERE a.ThisColumn = 'That';"

- Andrew

"Matt" <metal@rocks.com> wrote in message
news:dsr1hv0lfq9e13cuj4gvfunt67287j32sl@4ax.com...

> Hi,
>
> I'm trying to fill an ASP.NET DataGrid from a SQL-Server View. Note
> that this is a View and not a Stored Procedure.
>
> If i write the SQL instructions directly in the code, or if i use a
> stored procedure, it works great. But if the same SQL instructions are
> in a view, it won't work. Here it goes :
>
>
> public IDataReader SomeFunction()
> {
> SqlCommand ObjCmd = new SqlCommand();
>
> ObjCmd.Connection = m_ObjCon;
> ObjCmd.CommandText = "[Sales by Category]";
> ObjCmd.CommandType = CommandType.StoredProcedure;
>
> return ObjCmd.ExecuteReader();
> }
>
>
> It gives me an error, "The request for procedure 'Sales by Category'
> failed because 'Sales by Category' is a view object."
>
> My question is, is it possible to use a view instead of a stored
> procedure in this context? I'm a little confused about the difference
> between both. Thanks for help!
>
> Matt