The information in this article applies to:
SYMPTOMSAn OLE DB Provider created using the Visual J++ 6.0 and the OLE DB Simple Provider Toolkit does not work reliably. When attempting to use such a provider from ActiveX Data Object (ADO) via the Recordset.Open() method, the following error occurs: The following application error may occur when using the provider from a Visual J++ or Visual Basic client: The following application error may occur when using the provider from a Visual C++ client:
CAUSEThe Microsoft OLE DB Simple Provider component (Msdaosp.dll) does not properly implement COM reference counting. This causes erratic results with any client of the provider, because the provider may release itself when its real reference count is greater than zero. RESOLUTIONThis problem has been fixed with Microsoft Data Access Components (MDAC) 2.1 Service Pack 2 (SP2). You can download MDAC 2.1 SP2 from the following Microsoft Universal Data Access Web site: http://www.microsoft.com/data/download.htm STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. MORE INFORMATIONThe new release of MDAC also fixes a problem in the Java OLE DB Simple Provider, which causes access violation errors when using the Recordset.Delete() method. REFERENCESFor additional information, click the article number below to view the article in the Microsoft Knowledge Base: Q236044 Java OLE DB Simple Provider Crashes in Recordset.Delete() Method Additional query words: java osp ole db simple provider crash av recordset open method
Keywords : kbDatabase kbMDAC kbOLEDB kbOSP kbVJ600bug kbGrpVCDB kbDSupport kbMDAC210SP2fix |
Last Reviewed: October 1, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |