FIX: Errors When Accessing rdoPreparedStatements Not Consistent (154810)
The information in this article applies to:
- Microsoft Visual Basic Enterprise Edition, 32-bit, for Windows 4.0
- Microsoft Visual Basic Enterprise Edition for Windows 5.0
This article was previously published under Q154810 SYMPTOMS
If you attempt to access a non-existent rdoPreparedStatement, the error you
receive depends on whether there are other rdoPreparedStatements in the
collection.
If there are none, you will get this error:
40054 - invalid parameter.
If there is at least one, you will get this error:
40041: Couldn't find object indicated by text.
RESOLUTION
To minimize the impact of this problem, ensure that any error handlers that
may trap the preceding errors perform the same code for both errors.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This bug was corrected in Visual Studo 97 Service Pack 3. REFERENCES
Visual Basic Online help, search on: "CreatePreparedStatement; "rdoPreparedStatements".
Building Client/Server Applications with Visual Basic Manual, Chapter 8.
Modification Type: | Minor | Last Reviewed: | 3/14/2005 |
---|
Keywords: | kbbug kbfix KB154810 |
---|
|