I am using an ObjectDataSource to populate a GridView.  The ObjectDataSource 
accesses the data in the table by means of a Stored Procedure using a 
SQLCommand.ExecuteReader.  Does this mean that I can't easily do sorting, 
filtering and paging in my GridView

Bill

What kind of data do you bind against? IOW, what is the result of call by 
ObjectDataSource?

-- 
Miha Markic [MVP C#, INETA Country Leader for Slovenia]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/

"Bill Gower"  wrote in message 
news:OiJjtUX1HHA.4672@TK2MSFTNGP05.phx.gbl...

>I am using an ObjectDataSource to populate a GridView.  The 
>ObjectDataSource accesses the data in the table by means of a Stored 
>Procedure using a SQLCommand.ExecuteReader.  Does this mean that I can't 
>easily do sorting, filtering and paging in my GridView
>
> Bill
>
> 

Well,

  The good thing is that DataReaders are quite fast and you can tune it up 
so it performs like a rocket.

 Bad news are that you will need to make some extra code to support sorting 
and paging (you will make real paging just only selecting the records that 
are in the page).

  Here you have some useful links:

http://aspnet.4guysfromrolla.com/articles/031506-1.aspx
http://aspnet.4guysfromrolla.com/articles/032206-1.aspx
 
Good Luck
    Braulio

/// ------------------------------
/// Braulio Diez
///
/// http://www.tipsdotnet.com
/// ------------------------------




"Bill Gower" wrote:


> I am using an ObjectDataSource to populate a GridView.  The ObjectDataSource 
> accesses the data in the table by means of a Stored Procedure using a 
> SQLCommand.ExecuteReader.  Does this mean that I can't easily do sorting, 
> filtering and paging in my GridView
> 
> Bill
> 
> 
>