BUG: Data Control Errors Do Not Populate Error ObjectLast reviewed: September 17, 1996Article ID: Q129799 |
The information in this article applies to:
SYMPTOMSA "Type Mismatch" error is generated when a control is bound to a field with an incompatible type, but the Error object is not populated when it is examined in the Data Control Error event.
CAUSEThis is a limitation of the Data Control in Visual Basic version 4.0. When the DAO generates an error, the Error object is cleared when the Error event for the Data Control is fired.
RESOLUTIONFor more information, search for the "Trappable Data Access Errors" in the Help menu when building your error handling code. You are not prevented in any way from writing the exact same error handling code you would have written previously. Note that the error number passed as a parameter to the Data Control's Error will be correct. Only the Error object is affected. Also, most error checking in the DAO will be unaffected. If a Field or Database object generates the error, then the Error object is properly populated.
STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATION
Steps to Reproduce Problem
DataErr = 13 Description = HelpContext = 0 HelpFile = Number = 0 Source =If the Response = vbDataErrContinue is added to the program, the dialog will not pop up, but the output will be the same.
|
Additional reference words: 4.00 buglist4.00 vb4win vb4all
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |