Setting the Recordset's dynamic
Command Timeout Property does not time out the query.
Back to the top
One workaround for this problem is to switch the cursor from adUseClient to
adUseServer.
If adUseClient is necessary, another workaround is to use a Command object
as the source of the Recordset and use the Command object's
CommandTimeout property, for example:
'Assuming a connection object has been established
With oCm
Set .ActiveConnection = oCn
.CommandText = "select * from authors"
.CommandType = adCmdText
.CommandTimeout = 10
End With
With oRs
.CursorLocation = adUseClient
.Open oCm
End With
Back to the top
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article.
Back to the top