SQLClient has cross object code?

[Jonathan van de Veen]

I've build the following, of wich I know it's not the way it's supposed to be and I also know how to fix it. I'm just wondering how it's caused. - I open a SQLConnection - I create a SQLCommand - I run SQLCommand.ExecuteReader and store the readerobject in a variable - I set the SQLCommand to null - I create a new SQLCommand in the same SQLCommand variable - I run ExecuteNonQuery Doing the above will result in an InvalidOperationException with the message: "There is already an open DataReader associated with this Command which must be closed first." I looked to see if the setting to null and the creating a new SQLCommand actually resulted in a new object and it did. Just for my understanding, how does this work in the background?

[Colin Angus Mackay]

Jonathan van de Veen wrote:

Doing the above will result in an InvalidOperationException with the message: "There is already an open DataReader associated with this Command which must be closed first."

Command? Connection surely!

---

Upcoming Scottish Developers events: * UK Security Evangelists On Tour (2nd November, Edinburgh) * Developer Day Scotland: are you interested in speaking or attending? My: Website | Blog

[Jonathan van de Veen]

I'm affraid not. I've copied the message straight from VS.

[Nader Elshehabi]

Hello You should call the SqlDataReader.Close() first, or make a new command object.

Regards:rose:

[Jonathan van de Veen]

I was thinking the same thing, but... I can't close the datareader as I still need it. I tried making a new SqlCommand in a different variable, but this didn't solve the problem. I now have two connections wich I don't realy want.

[Nader Elshehabi]

Hello

Jonathan van de Veen wrote:

I now have two connections wich I don't realy want.

Sorry! It's not a perfect world!:-D

Regards:rose:

[Jonathan van de Veen]

Oh, I guess I took a wrong turn near Mars somewhere. :doh: