Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: Java OLE DB Simple Provider Crashes in Recordset.Delete() Method

View products that this article applies to.

This article was previously published under Q236044

↑ Back to the top


When using the OLE DB Simple Provider for Java, and when using the Recordset.Delete method, the following errors occur depending on the language that the recordset is used from:

In Visual C++

Unhandled exception in <program.exe> (MSDAOSP.DLL): 0xC0000005: Access Violation

In Visual Basic or Visual J++

The instruction at "<hex address>" referenced memory at "0x00000000". The memory could not be "read".

↑ Back to the top


This error is caused by an attempt to use an invalid rowset interface within DeleteRowsetHelper.

↑ Back to the top


This problem has been fixed with Microsoft Data Access Components (MDAC) 2.1 Service Pack 2 (SP2). You can the latest download MDAC from the following Microsoft Universal Data Access Web site:

↑ Back to the top


Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

↑ Back to the top

More information

The new release of MDAC also fixes a reference counting problem in the Java OLE DB Simple Provider, which causes unpredictable results and access violation errors (refer to the article in the References section).

↑ Back to the top


For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
225047� BUG: Java OLE DB Simple Provider Does Not Work Reliably

↑ Back to the top

Keywords: kbbug, kbdatabase, kbfix, kbmdac210sp2fix, kbmdacnosweep, KB236044

↑ Back to the top

Article Info
Article ID : 236044
Revision : 5
Created on : 5/17/2007
Published on : 5/17/2007
Exists online : False
Views : 390