Article ID: 304267 - View products that this article applies to.
This article was previously published under Q304267
This article has been archived. It is offered "as is" and will no longer be updated.
If you reference a field value in an ActiveX Data Objects (ADO) recordset when BOF or EOF is true, if you use late binding, and if you concatenate it to a string, an unhandled exception occurs in VBA6.DLL and causes an error.
Under Windows 95 or Windows 98, you receive the following error message:
Under Windows NT 4.0, you receive the following Dr. Watson error:
VB6 Has Caused An Error in VBA6.DLL
Under Windows 2000, Visual Basic quits.
An application error has occurred and an application error log is being generated. VB6.EXE. Exception: access violation (0xc0000005) address 0x0fa91abd
If you pass a reference to an ADO field value when BOF or EOF is true, the following error message normally appears:
However, if you reference a field value in an ADO recordset when BOF or EOF is true, if you use late binding, and if you concatenate it to a string, an unhandled exception occurs in VBA6.DLL and causes the above-mentioned error messages.
Either BOF or EOF is true, or the current record has been deleted. Requested operation requires a current record.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in Visual Basic 6.0 Service Pack 3.
Steps to Reproduce Behavior
Article ID: 304267 - Last Review: February 27, 2014 - Revision: 2.1