Results 1 to 3 of 3

Thread: library not registered -- but I'm using it

  1. #1
    Join Date
    Sep 2003
    Location
    in my cube
    Posts
    95

    library not registered -- but I'm using it

    Routine below dies on the "for each p" line, getting -2147319779 (8002801D) automation error, library not registered.

    The libraries in question ADO 2.5 and ADOX 2.5. I've even added the "installed version" reference in my project to see if that covers the interface exposure gap I'm experiencing (since I am using half of the above-mentioned library already). It's the reference that's bombing out, not the code. I'm unfortunately not in a position to re-install Office because I'm in a controlled corporate environment, but was hoping for a quick off-the-cuff fix that I could implement. I've attached a low-bandwith image of the references used.

    Private Sub IdentifyLinkedTables()
    Dim m_cat As ADOX.Catalog
    Dim t As ADOX.Table
    Dim p As ADOX.Property

    Set m_cat = New ADOX.Catalog

    m_cat.ActiveConnection = CurrentProject.Connection

    For Each t In m_cat.Tables
    If t.Type = "link" Then
    Debug.Print "-------------"
    Debug.Print t.Name
    For Each p In t.Properties
    Debug.Print p.Name
    Next
    End If
    Next

    Set m_cat = Nothing
    End Sub
    Attached Images Attached Images

  2. #2
    Join Date
    Sep 2003
    Location
    in my cube
    Posts
    95
    Changed the code and got around the error I was seeing. Not really a long-term fix because I still need to know what portions of the referenced library aren't being exposed, but I can live with the results for now.


    Private Sub IdentifyLinkedTables()
    Dim m_cat As ADOX.Catalog
    Dim t As ADOX.Table
    Dim p As ADOX.Property

    Dim i As Long
    Set m_cat = New ADOX.Catalog
    m_cat.ActiveConnection = CurrentProject.Connection

    For Each t In m_cat.Tables

    If t.Type = "link" Then
    Debug.Print "-------------"
    Debug.Print t.Name
    For i = 0 To t.Properties.Count - 1
    Debug.Print i & " - " & t.Properties(i)
    Next i
    End If

    Next

    Set m_cat = Nothing
    End Sub

  3. #3
    Join Date
    May 2006
    Posts
    1

    Smile Register msadox.dll

    I had the very same problem after a service pack update.

    Use the Windows/Start/Run dialog box to re-register the msadox.dll:

    Type in the following and select OK:
    regsvr32 "msadox.dll"

    You can also duplicate the error by unregistering the same dll:
    regsvr32 /U "msadox.dll"

    Be sure to rerun the FIX to get it working again...
    Last edited by gary.beyer; 06-01-2006 at 04:47 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •