That is not true. For one thing, the only states that Microsoft indicates
mean anything is Open and Closed. Their docs state that fetching is
"reserved for future use". My client uses fetching actually during the
reading of a row. However, the connection is in the open state while a
reader is reading a resultset and you can't use the connection while the
reader is open.
From: Joshua Mouch [mailto:joshua@stripped]
Sent: Sunday, December 12, 2004 1:15 PM
Subject: Multi-threading & Open connection
In a multi-threading environment, does a connection's state determine
whether or not it is available to be used by a process? My thinking is that
as long as a connection's state is either open or closed, then it is okay to
use it without fear of another thread being in the middle of using it.
Is this correct, or is there more going on then that (e.g. does the Fetching
state only get activated after the SQL command is sent instead of as the
command is sending)?
EmailScout Support Team