Forum Discussion
Force Access DB out of read-only mode
Hi,
One thing is if you are able to change the data in the linked table, e.g. add a record or change a field's content or a person in a record.
The other thing is the design of the table, like adding a new column:
"table is a linked table whose design can't be modified ... you must do so in the source database"
What are you doing to get this message? It is what you get when you try to change the design of any linked table in Access (not only Sharepoint). Sharepoint is even an exemption from the rule as in datasheet view of the linked table you can change parts of the design via the Fields tab of the ribbon. But I'm not sure why you would want that.
Servus
Karl
*********
http://AccessDevCon.com
https://www.donkarl.com
I can add and edit data in the Access table and that is reflected in the SP list, so that works fine. It is the Excel upload that doesn't work.
If I have opened the table, the error message occurs immediately when I change to Design View.
Charles
Karl_Donaubauer George_Hepworth
I guess silence = no-can-do! I would have thought automated updates to SP lists was a pretty usual thing to want to do, so I will try to find an alternative method (any suggestions welcome!).
Many thanks for your kind attention to this!Charles
- Silence is a message itself.
You are experiencing a problem with uploading Excel data into SharePoint lists. Both are at the perimeters of my knowledge in the first place. In addition, data problems tend to be harder to suss out anyway because, well, the data itself is part of the context and since we can't see that data, it's harder to try things out.
In the initial question, you suggested "forcing Access out of read only mode", but that hardly seems to be the problem, nor would it be the solution, IMO. The problem appears to be in either the imported Excel data or in the table/SharePoint list or both.
FWIW, I recently tried to move a table with calculated fields to SharePoint. Access handles the locally defined calculated values (concatenation of First and Last Names of People). SharePoint shows an error when that same calculation is ported over to the SP list. I can then "correct" it in SP so it shows there, but then the linked SP list raises an error every time I try to open it in Access. I don't know why. It does suggest to me that although basic tables/lists are okay, the internal differences between the way tables are handled and the say SP lists are handled are tricky.
I'm going back to the Excel data as the most likely source of your problem, but that's 90% a guess.Thanks George_Hepworth and Karl_Donaubauer
I hope my reply wasn't misunderstood - my apologies if it was - your replies have helped me and I am grateful to you both! I guess silence is a message - it just takes a good ear to catch the nuances!
My original plan was a macro to append directly to the SP list, but I couldn't find any guidelines on linking to SP Online and then found this blog https://scottlyerly.wordpress.com/2014/05/14/excel-geeking-using-vba-and-ado-to-pull-data-from-sharepoint-lists/ that suggested I never would.
So I diverted to Access and had that running in my local environment by converting the Access table to a local table and converting the UserInfo column to text in Access. But I can see now that I would run into the problem George_Hepworth sketched in the example - if I get it working in Access, then it won't work in the SP list, and vice versa.
I'd imagined this was a pretty straightforward thing to do, but I'm wiser now!
Many thanks again!
Charles
Hi,
My personal silence = I have no idea what you are trying to accomplish. That's why I let others answer who understand you better. So far there was just no crowd. 😉
Servus
Karl
*********
http://AccessDevCon.com
https://www.donkarl.com
