Any insight would be greatly appreciated...It seems to me like the ADO
connection object can only execute one database action at a time regardless
of whether the operation is launched async or not..
Thanx,
Shannon Richards
BBA, AIT, MCP
*** NOTE ***
If the active connection gets closed or dies while a command is executing
the program (COM+DLL in my case) will crash and VB will cause a "Dr.Watson"
error and will terminate the application and log the error in the system
log. This seems to be a bug in my opinion because there is no possible way
to trap this error before the application terminally fails.
The best error handling method I can think of is simply eliminating the
ability to close the connection if there is a command executing on it...or
canceling the executing commands and then closing the connection. This
however does not help in a situation where the connection dies for an
unknown reason (Like IT reboots the server while clients are connected)
Thanx,
Shannon Richards
BBA, AIT, MCP
"BIG555" <sricha...@hotmail.com> wrote in message
news:#7smH24cBHA.2388@tkmsftngp07...