Article ID: 276270 - View products that this article applies to.
This article was previously published under Q276270
This article has been archived. It is offered "as is" and will no longer be updated.
Advanced: Requires expert coding, interoperability, and multiuser skills.
When you work with the DataSourceControl (DSC) of an Office Web Component, you may specify a CommandTimeOut value for the Connection object. When you then build a query or RecordsetDef based on the Connection object, your CommandTimeOut value is ignored. The operation times out at the default value of 30 seconds.
To resolve this problem, obtain the latest service pack for Microsoft Office 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/276367/EN-US/ )OFF2000: How to Obtain the Latest Office 2000 Service Pack
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Office 2000 Service Pack 2.
To temporarily work around this problem, set the CommandTimeOut property for individual Command objects rather than for the Connection object.
For more information about the CommandTimeOut property, please visit the following Microsoft Web site:
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/243464/EN-US/ )CommandTimeOut Expired Error
Article ID: 276270 - Last Review: February 28, 2014 - Revision: 3.2