The information in this article applies to:
SYMPTOMSIf a Connection's CommandTimeout property is set to some value and a Command object is associated to that Connection, the Command object does not pickup the Connection's CommandTimeout setting. Instead, the Command object's CommandTimeout is set to it's default setting or whatever it was set to prior to being associated with the Connection. CAUSEActiveX Data Objects (ADO) does not practice inheritance. Due to the stand alone capability of it's objects, a Command object can be associated with more than one Connection object. The one exception is the CursorLocation property. RESOLUTIONSpecifically set the Command object's CommandTimeout. STATUSThis behavior is by design. MORE INFORMATIONSteps to Reproduce Behavior
Additional query words:
Keywords : kbADO150 kbADO200 kbDatabase kbGrpVBDB kbGrpMDAC kbDSupport kbADO210sp2 |
Last Reviewed: November 16, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |