BUG: Data Control Errors Do Not Populate Error Object (129799)
The information in this article applies to:
- Microsoft Visual Basic Standard Edition, 32-bit, for Windows 4.0
- Microsoft Visual Basic Professional Edition, 16-bit, for Windows 4.0
- Microsoft Visual Basic Professional Edition, 32-bit, for Windows 4.0
- Microsoft Visual Basic Enterprise Edition, 16-bit, for Windows 4.0
- Microsoft Visual Basic Enterprise Edition, 32-bit, for Windows 4.0
This article was previously published under Q129799 SYMPTOMS
A "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.
CAUSE
This 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.
RESOLUTION
For 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.
STATUS
Microsoft 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.
Modification Type: | Major | Last Reviewed: | 12/9/2003 |
---|
Keywords: | kbbug KB129799 |
---|
|