I have an application that occasionally throws up an "open datareader
associated with this connection". Obviously there is a path that leads to a
datareader being left hanging; however finding it will be difficult since
there are lots of different ways to go around the application and knowing
which database operation was carried out immediately before the one
generating the error is difficult. The error is very rare, which adds to the
difficulty.
Since the system is aware of the datareader, there must be a way that for an
arbitrary connection object (ODBC in this case), I can locate any connected
datareader. How would I go about this in VB.NET?
--
Dr. Craig Graham, Software Engineer
Advanced Analysis and Integration Limited, UK. http://www.aail.co.uk/
