After you do your dr.Close() try also calling Dispose and setting it to
null. That should help ensure that the object is definitely not using the
previous one.

In this case though, I don't think you'll gain anything by re-using the same
variable. You'll still end up using separate data connections so you
shouldn't really get any benefit.

If these items are at all similar and you really wanted to re-use resources,
you could see if you can combine them into one stored procedure that can
call the other two stored procedures. This lets you get the first data, then
use the NextResultset method to attempt to load the second set of data. This
re-uses the connection and reduces the roundtrip. The NextResultset will
return a true if there is a next resultset and a false otherwise so it lets
you test to ensure that the data was really returned before you attempt to
read it. This may not be at all what you are trying to do, but since you
were eager to re-use resources I thought I'd mention it. It's a great little
trick especially when attempting to load similar data, such as when you're
trying to populate lists of data for a particular form (such as states,
countries, etc.).

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - Expression

A DataReader is a forward-only read-only set of data. You have only one
opportunity to make use of it. Once you've read to the end, that's it - you
can't go back... This has the effect of making the DataReader object very
light and, generally, speaking, it will out-perform other types of data
sets...

Therefore, if you need anything other than a one-time-only read of the data,
then a DataReader is the wrong ADO.NET object.

Try a DataSet instead...

Alternatively, if the amount of data in the DataReader is (relatively)
small, you could always read it into another object, maybe a generic...