Forum Discussion
Access connected to sharepoint list
- Dec 06, 2020
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.
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_HepworthNov 15, 2020Silver Contributor
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.
- thanssonNov 16, 2020Copper Contributor
- George_HepworthNov 19, 2020Silver Contributor
A total of 3,000 rows isn't huge, even for SP, so I'd be back to looking at two possibilities.
You mentioned this is a delete query? Are you deleting every record in the list, or using a filter to select some subset of the total? If it is 3,000 and that's all of the records, that is one thing. If it is a filtered subset of a larger number, that will be slower, and potentially very slow.
The other possibility is that something else in your environment changed. Unfortunately that often happens and we don't know about it until problems pop up. Since we can't see the system nor what might have changed, we would have to rely on the SharePoint admins for information.