Forum Discussion
Move Existing Sharepoint Linked Database to a different Sharepoint Site
Hi. I have a Sharepoint Linked Database that is working well within our company. We would like to use it within another subsidiary company that operates with its own Name and Sharepoint sites. Could you please assist as i am struggling to do this. Thanks
5 Replies
George, thanks for the prompt response.
I have done the following -- Made a copy of the Access file.
- Created the new Sharepoint site.
I have been trying to export the Access file to the new Sharepoint site but i get the error message that i need to review the 'Trust Settings'. To be honest i am struggling because i haven't an idea how i should be going about this.
I will have a go at the steps above and see how it goes. Thanks
Trust settings refer to the location of the accdb on your computer. You have to designate the folder where the Front End accdb is stored as a Trusted Location. You must have done that already for the existing deployment. Take a look at how that was done.
You will not actually export the Access file itself to the new SharePoint site. You will only link it to the new SharePoint lists there.
When you do that, a dialog will open asking you for the location of the SharePoint lists. Enter the URL and select the lists/tables. This is assuming that you have already created the lists needed for the subsidiary on their SharePoint site.
Ok, at the moment the copied access file is still linked to the original Sharepoint lists. When you say create new sharepoint lists in the new sharepoint site, do you have to do this manually or is there a way to copy the lists between sites? (i am currently searching the web for methodology)
It would help us to help you if we knew what struggles, specifically, you have encountered.
In theory, the steps would involve
- Recreating the SharePoint lists for the database application on the subsidiary's SharePoint site.
- Creating a copy of the accdb Front End with whatever customization is needed, such as replacing organization names in labels, etc.
- Putting that accdb Front End on a computer in the Subsidiary's network. This can take various paths, so tell us what you tried and what happened.
- Relinking that accdb Front End to their SharePoint links.
- Putting a copy of that master accdb Front End on the computer of each intended user.
Where in that path, specifically, did you encounter problems?
