Forum Discussion

thansson's avatar
thansson
Copper Contributor
Nov 13, 2020

Access connected to sharepoint list

Hi


I have 2 list I update from Access to sharepoint.

First list I run 3 query (Add, Update, Delete) no problems.

 

Second Liste the same 3 query (Add, Update, Delete).

When i come to the last Query Delete most of the times I get the failure (Cannot update, database or object is read only)

If i keep running the query sometimes it will work. ( Ivahe set the cache to "Never")


Did anyone have this issue?


Regards

Tony

  • George_Hepworth's avatar
    George_Hepworth
    Silver Contributor

    thansson 

     

    One possibility, based on that brief overview, is that the SharePoint list is still being locked from the previous query while some process continues, possibly re-indexing or something like that. What happens if you wait longer between running the various queries? 

    How many records are in these lists? SharePoint is definitely handicapped when processing larger lists. The exact meaning of "larger" can be flexible but anything over 5,000 records might be venturing into that territory. Definitely anything over 25,000 records in a SharePoint list is going to be suspect--performance wise.

    • thansson's avatar
      thansson
      Copper Contributor

      Hi George_Hepworth 

       

      tks for your anser.

       

      Numbers of Rows is different each time, but around 3000 Rows.

       

      It dont help if I am waiting, if  I close access and reopen, and only run the last query, still the same. If I keep on running the query it Will loose connection, and after that the query has Been executed.

       

       

      It is Strange it has Been working for a while without problems.

       

       

       

      • George_Hepworth's avatar
        George_Hepworth
        Silver Contributor

        thansson 

         

        How many rows are in that SharePoint list, in total?

         

        While 3,000 is less than the  typical 5,000 where we often see slowdowns in SharePoint lists with Access, if that is 3,000 ADDITIONAL rows, you might well be over-taxing the SP lists.

         

        What you describe suggests that you are approaching, or have passed, some threshold number of records. 

         

        If that's not it, I'd be looking at things like network connections, and so on that can impact performance.

Resources