Cannot convert type 'char' to 'System.Data.DataRow'

is the message i receive when attempting to compile the following statement:

foreach(System.Data.DataRow dr in myDataSet.Tables[0].DefaultView.RowFilter ="Status_FK = 1")

Basically, I'd like to use an existing dataset, apply the rowfilter, and then iterate through the filtered rows.

LVL 7
brdrokAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AlexFMCommented:
I guess it should be something like this:

myDataSet.Tables[0].DefaultView.RowFilter ="Status_FK = 1";

foreach(System.Data.DataRow dr in myDataSet.Tables[0].DefaultView)
{
    ....
}



0
brdrokAuthor Commented:
Thanks unfortunately i get an error message that says:

Specified cast is not valid....

wish i could get a better error description....

0
Razzie_Commented:
I think it should be corrected a little bit to:

myDataSet.Tables[0].DefaultView.RowFilter ="Status_FK = 1";

foreach(System.Data.DataRow dr in myDataSet.Tables[0].DefaultView.Table.Rows)
{
   ....
}

does that work?
0
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

brdrokAuthor Commented:
Hey Razzie,

I think the suggestion of yours is very close....at least I stopped getting the error message, however, the foreach statement seems to go through every single datarow and not the filtered rows.  so i wrote a couple messagebox functions that shows me the number of records and here is that i came up with

MessageBox.Show(myDataSet.Tables[0].DefaultView.Count.ToString());   <--returns 12, which sounds about right

MessageBox.Show(myDataSet.Tables[0].DefaultView.Table.Rows.Count.ToString()); <--returns 118, which are all the records

foreach(System.Data.DataRow dr in myDataSet.Tables[0].DefaultView.Table.Rows)
{
    //goes through all 118 records....
    ..........................
}

time for me to buy a good ado.net book :)


0
Snarf0001Commented:
If the view being filtered isn't really important for anything else, then use the DataTable.Select command instead:

foreach(System.Data.DataRow dr in myDataSet.Tables[0].Select("Status_FK=1"))
{
}

This will return a collection of datarows matching the criteria which you can iterate through.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
brdrokAuthor Commented:
Snarf0001:

thanks...works really well right now.  If you don't mind explaining in layman's term...what exactly is the difference between the RowFilter and the "Select" methods?  

thanks

0
Snarf0001Commented:
No problem.

The rowfilter is used on the dataview, which generally is used for filtering on bound controls, ie eliminating rows from a bound drop down or something like that.  Dataviews CAN be used for processing data like you want to, but it's more of a pain, as that's not really what they were designed to do.

The .select will do basically the same thing as the rowfilter, but it's performed on the actual datatable itself, not the dataview, and will return an array of datarows for processing or whatever you might want.

Primarily, rowfilter acts on the view, and is used for changing display, .select acts on the table, returns an external set for processing.
0
brdrokAuthor Commented:
I think I understand....basically when using the .select...we are making another call to the database....but when using the rowfilter...the processing is being done on the cpu and no call to database is being made...

0
Snarf0001Commented:
no no, the select is not going back to the db.  The datatable itself is still in memory in the app, with all of it's datarows.  Each one can have multiple dataviews, which just play around with the data in memory in the datatable.
A select statement, will just make a collection out of certain rows in memory.  Still no trip to the db.
The datatable is the only thing that actually HAS the data, the view just manipulates it, and a .select just exposes some of it.
0
brdrokAuthor Commented:
gotcha....those are some real knowledge gold nuggest today :)

is there a particular syntax that will release the collection of certain rows in memory or should i leave that up to the garbage collector?

too bad i already closed the question or else i could have added a few more points or uploaded a six pack of beer...

0
Snarf0001Commented:
lol

Leave the rows up to the garbage collector.  They're still actually attached to the datatable, but I wouldn't really worry about that at this point.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
C#

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.