Solved disconnected from server

[collins_jd]

All of the sudden after working fine for the last 2 years, when we try to finish the order or add another product we get the following error message: "you cannot reference rows created when you are disconnected from the server because this violates the lookup settings defined for this table or list. please connect all tables with the server and try again.". I have refreshed and relinked the sharepoint tables. The form says "online with sharepoint" i cant find a disconnect.

 

[GPGeorge]

All of the sudden after working fine for the last 2 years, when we try to finish the order or add another product we get the following error message: "you cannot reference rows created when you are disconnected from the server because this violates the lookup settings defined for this table or list. please connect all tables with the server and try again.". I have refreshed and relinked the sharepoint tables. The form says "online with sharepoint" i cant find a disconnect.

View attachment 118756

There is some network problem that interrupts your connection to the SharePoint lists.

What do you have set for Caching here:

 

[collins_jd]

There is some network problem that interrupts your connection to the SharePoint lists.

What do you have set for Caching here:

View attachment 118757

where do i find that? in access or online in sharepoint?

 

[collins_jd]

There is some network problem that interrupts your connection to the SharePoint lists.

What do you have set for Caching here:

View attachment 118757

here is what mine shows

 

[Gasman]

Doesn't one negate the other?

 

[collins_jd]

Doesn't one negate the other?

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.

 

[GPGeorge]

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.

 

[collins_jd]

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.

oh my goodness!! that worked!! THANK YOU!!!! I knew the number of records was going to become a problem so now that this issue is fixed im working on how to "archive" old ones so they can still be referenced when needed. Trying to decide the easiest way since i have so many other queries and forms pointing to the order and order detail table. Thank you so much again for your help!

 

[GPGeorge]

oh my goodness!! that worked!! THANK YOU!!!! I knew the number of records was going to become a problem so now that this issue is fixed im working on how to "archive" old ones so they can still be referenced when needed. Trying to decide the easiest way since i have so many other queries and forms pointing to the order and order detail table. Thank you so much again for your help!

I'm delighted to hear that you are back on track. Continued success with the project.