Microsoft KB Archive Search

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.

  1. Home
  2. Jet 4.0 OLE DB Provider requires a Jet 4.0 system database

Jet 4.0 OLE DB Provider requires a Jet 4.0 system database

View products that this article applies to.

Advanced: Requires expert coding, interoperability, and multiuser skills. This article applies only to a Microsoft Access database (.mdb).

For a Microsoft Access 2002 version of this article, see 286376� (http://support.microsoft.com/kb/286376/ ) .
For a Microsoft Access 2000 version of this article, see 243466� (http://support.microsoft.com/kb/243466/ ) .
For a Microsoft Access 2002 version of this article, see 286376� (http://support.microsoft.com/kb/286376/ ) .
For a Microsoft Access 2000 version of this article, see 243466� (http://support.microsoft.com/kb/243466/ ) .

↑ Back to the top

Symptoms

When you try to use a Microsoft Jet 3.0 and later Workgroup Information file (system database) with Microsoft Jet 4.0 OLE DB Provider, you may receive the following error message:
Run-time error '3251':

Object or provider is not capable of performing requested operation.

↑ Back to the top

Cause

The OLE DB application programming interfaces (APIs) make calls that are not supported in the Jet 3.0 and later installable indexed sequential access method (IISAM).

↑ Back to the top

Resolution

You must use the Workgroup Administrator utility in Access 2003 to create a new Workgroup Information file. You must re-create all user accounts and all group accounts. You must use the exact account names and the exact personal identification numbers (PIDs) that were used to create the user accounts and the group accounts in the earlier version of Access.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
278329� How to run the Workgroup Administrator program

↑ Back to the top

Status

This behavior is by design.

↑ Back to the top

More information

Steps to Reproduce the Problem
  1. Create the c:\Test folder on a computer with Access 2003 installed.
  2. Copy the System.mdw file and the Northwind sample database file from the computer that has Access 97 installed to the Test folder that you created in step 1.

    By default, the Access 97 System.mdw file is stored in the Windows\System folder (or for Microsoft Windows NT, in the Winnt\System32 folder).
  3. Start Access 2003.
  4. Create a new database.
  5. Create a new module in the database.
  6. On the Tools menu, click References, and then select the following references:
    • Microsoft ActiveX Data Objects 2.1 (or later) Library
    • Microsoft ADO Ext. 2.5 (or later) for DDL and Security
  7. Type the following function in the new module: 
    Option Compare Database

    Option Explicit


    Function fncTest()
    
    Dim conn As ADODB.Connection
    
    Dim cat As ADOX.Catalog
    
    Dim grp As ADOX.Group
    
    
    Set conn = New ADODB.Connection

    
    conn.Provider = "Microsoft.Jet.OLEDB.4.0"
    
    conn.Properties("Jet OLEDB:System database") = "C:\Test\System.mdw"
    conn.ConnectionString = "Data Source=C:\Test\Northwind.mdb;" & _
                            "User Id=Admin;Password="
    
    conn.Open

    
    Set cat = New ADOX.Catalog

    
    cat.ActiveConnection = conn

    
    Set grp = New ADOX.Group
    
    
    For Each grp In cat.Groups    '<== error occurs here
        
    Debug.Print grp.Name
    
    Next grp

    End Function
  8. Press CTRL+G, and then type the following line:
    ?fncTest()
  9. Press ENTER.

    You receive the error message that is in the "Symptoms" section.

↑ Back to the top

References

For more information about the Workgroup Information file, click Microsoft Office Access Help on the Help menu, type workgroup in the Search for box in the Assistance pane, and then click Start searching to view the topic.

↑ Back to the top

Keywords: KB824261, kbprb, kberrmsg, kbnofix

↑ Back to the top

Article Info
Article ID : 824261
Revision : 4
Created on : 6/21/2004
Published on : 6/21/2004
Exists online : False
Views : 346