All worked fine yesterday..sqldatareader yet again

[kleinma]

Perhaps what is going on is the DataReader is being closed because you are closing the DB connection associated with it?

That is the only thing that seems to make any sense. You are closing the connection to the database, which the DR needs, so the DR closes as well??

That is just a guess, but it seems to make sense... set a watch on your lRead.IsClosed property when you are in your UseSQLDBExecuteReader, and see if it changes from open to closed as your finally runs. Also even if you remove the finally, the connection is going out of scope when your function ends, which would explain why even if you remove the finally it still happens?

[JAKSupport]

Perhaps what is going on is the DataReader is being closed because you are closing the DB connection associated with it?

That is the only thing that seems to make any sense. You are closing the connection to the database, which the DR needs, so the DR closes as well??

That is just a guess, but it seems to make sense... set a watch on your lRead.IsClosed property when you are in your UseSQLDBExecuteReader, and see if it changes from open to closed as your finally runs. Also even if you remove the finally, the connection is going out of scope when your function ends, which would explain why even if you remove the finally it still happens?

Why would it work then if I move the debugger doesnt it still lose the scope since the function ends?
That doesnt make any sense its valid when I move the debugger to the "end try" line of the finally statement without hitting the actual dispose and close methods...yet if I even comment them out and run the same code..it fails?

How would you go around returing lRead then ? I do not want to maintain a connection to the db as this reduces the performance of this entire class...