FIX: MDAC 2.1 SP1 Problem Executing Access Query with Wildcard

ID: Q245343

The information in this article applies to:

ActiveX Data Objects (ADO), versions 2.1 SP1, 2.1 SP2, 2.5
Microsoft Visual Basic Enterprise Edition for Windows, versions 5.0, 6.0

SYMPTOMS

In Access the asterisk(*) is the normal wildcard character. However, in Visual Basic with MDAC 2.1 SP1 (version 2.1.1.3711.11(GA)) installed, when calling an Access query using this wildcard character through ADO and the Access ODBC driver, it fails to return any records.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug is corrected in MDAC 2.1 SP2 (2.1.2.4202.3 (GA)), which can be downloaded from here:

http://www.microsoft.com/data/

MORE INFORMATION

Steps to Reproduce Behavior

Create the Access Query

In Access 97 or Access 2000, create a query, Query1, with the following SQL statement in the Nwind.mdb or NorthWind.mdb database:


Select * From Customers Where Customer ID LIKE 'A*'

This should return all of the customer records (4 in all) with a Customer ID that starts with "A".

Visual Basic Test Application

Start a new project in Visual Basic and choose Standard EXE. Form1 is created by default.

Using the Project and References menu, add a reference to the following type library:
Microsoft ActiveX Data Objects 2.1 Library

Add a Command button (Command1) and the following code to the form:


Option Explicit

Private Sub Command1_Click()
Dim cn As ADODB.Connection, rs As ADODB.Recordset, cmd As ADODB.Command

  Set cn = New ADODB.Connection
  Set cmd = New ADODB.Command
  Set rs = New ADODB.Recordset

  cn.Open "Driver={Microsoft Access Driver (*.mdb)};" & _
          "DBQ=C:\Program Files\Microsoft Visual Studio\VB98\nwind.mdb"

  With cmd
    .Name = "Query1"
    .CommandText = "Query1"
    .CommandType = adCmdStoredProc
    Set .ActiveConnection = cn
  End With

  rs.CursorLocation = adUseClient
  rs.Open cmd
  Debug.Print rs.RecordCount

  rs.Close
  cn.Close

End Sub

You need to change the path to Nwind.mdb in the connect string to point to the database you modified.

Run the application and click the Command button. On systems with older versions of MDAC 2.1, 0 is returned as the record count. With the later version of MDAC 2.1, the correct number, 4, is returned.

Additional query words: dbado21fix KbGrpMDAC kbGrpVB kbGrpVBDB kbdsupport

Keywords : kbGrpVBDB kbGrpMDAC kbDSupport kbMDAC250fix
Version : WINDOWS:2.1 SP1,2.1 SP2,2.5,5.0,6.0
Platform : WINDOWS
Issue type : kbbug