it does sort of read that way but i have not touched these settings. we have been using this for 2 years from 4 different office locations with no issue until 2 weeks ago. At first I thought it was records number issue as we have reached and passed 5000 lines but some of the tables have 8000 and working fine. its just one that isnt working.
That setting is preventing offline caching from being used for your linked SharePoint lists.
It was probably set that way to alleviate performance problems which can arise when Access has to maintain the local cache. With increasingly larger data sets, that's an an increasingly problematic situation.
What no caching means, on the down side, though, is that when there is an interruption in the network connection, processing stops because Access has to wait for the connection to be restored.
I suspect this could be a combination of intermittent network drops that don't show up in your Access interface and no caching, which prevents offline processing to be synched when the network comes back.
Also, when the number of records grows in SharePoint, performance can be impacted.
So, try this, please. As a test, uncheck the option "Never Cache" and observe whether that problem is alleviated. Be prepared for initial slowdown in starting Access, though, as updating the cache will take some time. What we need to know is whether it impacts the network dropping problem.
