Results 1 to 3 of 3

Thread: Reading a SharePoint list using Excel VBA

  1. #1

    Reading a SharePoint list using Excel VBA

    I am having an issue pinning down why one machine can access a SharePoint list using the code below but another cannot.

    The code below works fine on my PC and laptop but not on a collegue's laptop. The error returned is ...

    "Run-time error: '-2147467259 (80004005)';
    "Could not find installable ISAM"

    Googling has told me to try ...

    • Adding "Extended properties=" and single speech marks around the list of items after Provider (as seen in the code below) = Same error occurred.
    • Installing the Microsoft Access Database Engine 2010 Redistributable (have tried both 32bit and 64bit) = Neither made a difference.
    • Going to the SharePoint site via Internet Explorer and logging in (to establish credentials) = Can get to the site but doesn't help the Excel code to run.

    The machines where it works are Microsoft 365 (Business version). Latest version that Update can find.

    The machine where it doesn't work is Microsoft Office 2016 for Home and Business. 32 bit installation.

    Is there anything else I can try?

    sConn = "Provider=Microsoft.ACE.OLEDB.12.0;" & _
    "Extended Properties='WSS;IMEX=1;RetrieveIds=Yes;" & _
    "DATABASE=" & sSHAREPOINT_SITE & ";" & _
    "LIST=" & sDEMAND_ROLE_GUID & "';"
    ' Create some new objects.
    Set cn = New ADODB.Connection
    Set rs = New ADODB.Recordset
    ' Open the connection.
    With cn
         .ConnectionString = sConn
    End With


  2. #2
    VBAX Guru mancubus's Avatar
    Dec 2010
    "Where I lay my head is home" :D
    after googling;

    The issue "could not find installable ISAM" using the "Microsoft.ACE.OLEDB.12.0" data provider is caused by "ISAM drivers are used by Access to update file formats other than its own. If the path of the ISAM driver in your Windows Registry is not valid, or if the ISAM driver does not exist, the problem may occur."

    i am not familiar with querying sp lists.
    maybe above links will give you an idea.
    the second link is about registries.
    Last edited by mancubus; 09-28-2021 at 04:59 AM.

    1) Posting Code
    (or paste your code, select it, click # button)

    2) Uploading File(s)
    Go Advanced / Attachments - Manage Attachments / Add Files / Select Files / Select the file(s) (multiple files can be selected while holding Ctrl key) / Upload Files / Done
    Replace company specific / sensitive / confidential data. Include so many rows and sheets etc in the uploaded workbook to enable the helpers visualize the data and table structure. Helpers do not need the entire workbook.

    3) Testing the Codes
    always back up your files before testing the codes.

    4) Marking the Thread as Solved
    from Thread Tools (on the top right corner, above the first message)

  3. #3

    Thanks for those. I had seen the first one before but it hadn't helped. The second one is new but relates to Excel rather than SP as the source. Not sure editng the registry is a good way to go, especially as I won't be allowed to for some of the potential users.

    I did find a workaround, removed 2016 and went to full 365 and the error stopped. Again, not an ideal solution as may not always be in my control but I am pretty certain the vast bulk of the users will have full 365.

Tags for this Thread

Posting Permissions

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