Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: CommandTimout Property Problem with Connection Object


View products that this article applies to.

Symptoms

The Connection object of the ActiveX Data Objects supports the CommandTimeout property. This property is documented to support a value of 0, which provides for an infinite timeout. This functionality is not available in ActiveX Data Objects 1.0.

↑ Back to the top


Resolution

The CommandTimeout property functions properly for all values other than 0. If you wish an infinite timeout, you will need to use this parameter in conjunction with the Command object instead. The following example demonstrates how to set the Command object's timeout:
   Set MyConn = Server.CreateObject("ADODB.Connection")
   MyConn.ConnectionTimeout = 0
   MyConn.CommandTimeout = 0 ' *** THIS HAS
    *** NO EFFECT BECAUSE OF THE BUG ***
   MyConn.Open ConStr, UserId, PassWord
  
   Set cmdTemp = Server.CreateObject("ADODB.Command")

   ' *** T H I S   L I N E   W A S   A D D E D ***
   cmdTemp.CommandTimeout = 0 ' *** SETTING IT TO ZERO CAUSES IT TO WAIT
    FOREVER ***
				

NOTE: The CommandTimeout property on an ADO connection object has no effect on the CommandTimeout property setting of the command object on the same connection. Essentially, the command object's CommandTimeout property does not inherit the value of the connection object's CommandTimeout value.

In order for cmdTemp.CommandTimeout = 0 to work properly, you must use the command object to execute the query.

↑ Back to the top


Status

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

This bug was corrected in MDAC 2.6.

↑ Back to the top


More information

The following code attempts to set the timeout to 0. When set to this value, the connection object should provide for an indefinite amount of time before timing out. It does not.
   <%
   Set cn = Server.CreateObject("ADODB.Connection")
   cn.CommandTimeout = 0
   cn.Open "datasourcename", "userid", "password"
   cn.Execute("SQL statement that would cause a timeout")
   %>
				

↑ Back to the top


References

For the latest Knowledge Base articles and other support information on Visual InterDev and Active Server Pages, see the following page on the Microsoft Technical Support site:

↑ Back to the top


Keywords: kbaspobj, kbbug, kbcodesnippet, kbdatabase, kbfix, kbmdac260fix, kbmdacnosweep, kbado260fix, KB175264

↑ Back to the top

Article Info
Article ID : 175264
Revision : 4
Created on : 5/2/2006
Published on : 5/2/2006
Exists online : False
Views : 452