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

Symptoms

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

Cause

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

↑ Back to the top

Resolution

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:

http://msdn2.microsoft.com/en-us/data/aa937695.aspx

↑ Back to the top

Status

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