No, you can't bind a DataReader to a DataGrid in a WinForms application.
Why would you want to?
I mean, the data retrieved should be stored somewhere.
So, why store data into the grid (as you want)?
Isn't storing the data in universal container such as dataset a better
approach (rhetorical question ;-))?
In this way, grid (each grid) doesn't need to provide its own data container
and data is stored in a way that other controls can use it.
William Ryan eMVP said:Hi Scott:
I see the others have answered your question but I'd like to mention the new
stuff in ADO.NET 2.0 that addresses this issue. Also, you could create a
Subclassed grid, simple inherit from DataGird and you can come up with your
own method to load the grid from a Reader if you really need this
functionality. You're going to have to bind it to a
datatable/dataset/dataview or some other IList object (Actually my memory is
foggy now but I think you can bind to anything that implements IList) or
strongly typed collection. So you can build a datatable from the reader or
build a collection from it and bind to either of those but it'll take some
work. Since Readers work best for read only scenarios and grids are usually
used for editing in the winforms context -probably not a big need for this
whereas on the web there is b/c it's usually a read only scenario (and
although you can 'edit' in a web grid, the underlying story is a bit
different which makes the reader a nice choice)
In ASP.NET you are allowed to bind to a reader, actually
dataGrid.DataSource = myCommand.ExecuteReader(); It handles the
while(reader.Read()) for you and builds a datatable. It's a clunky
implementation though b/c the reader may not have any rows so you have to
put in an extra check to verify the grid will have something in it.
In ADO.NET 2.0 you can do something similar with the DataTable's .Load
method. You can load a DataTable from a DataReader WITHOUT reading through
it. So assuming I just called ExecuteReader on a reader named dr I could to
this:
DataTable dt = new DataTable("TableFromReader");
dt.Lead(dr); //Didn't have to do anything other than call ExecuteReader
before this somewhere
DataGrid1.DataSource = dt; //Will work in Winforms!
You can also do the reverse, get a Reader from a DataTable!!!!!
The DataTable has a GetReader method , which will give you a DataReader
from a DataTable
I have some examples of all of this here
http://www.knowdotnet.com/articles/miscadonet.html
or here
http://msmvps.com/williamryan/archive/2004/07/14/10090.aspx
--
--
W.G. Ryan, eMVP
Have an opinion on the effectiveness of Microsoft Embedded newsgroups?
Let Microsoft know!
http://www.devbuzz.com | http://www.knowdotnet.com
https://www.windowsembeddedeval.com/community/newsgroups
John Dann said:Well, I can well believe that you're right and quite possibly I'm not
approaching this in the best way conceptually.
But the project calls for a subset of data from a large database to be
bound to a chart. Especially in development but also to some extent in
subsequent use I can imagine that it will be quite useful to
crosscheck unexpected chart results against the underlying data.
(Especially when, as real-time instrumental data, it won't be feasible
to rigorously validate all data that's added to the database.) The
chart might need to be refreshed every minute or more frequently and a
datareader seems to be the fastest way to make a selection from a
database that might run to a million rows or more. But creating a
dataset from the datareader and then binding that to a Datagrid in
order to visualise the data in numeric terms seems an unnecessary and
potentially slow step. Hence why I was looking for a way of binding
the datareader directly to a read-only grid.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.