Moving an Access Database to Sharepoint
I have one of these typical scenarios where user has an ancient Access application where the person who made it is no longer around. The goal is to move this application to the cloud, so we are assuming Sharepoint.
We have tried moving the application files to other locations on the network or local machine and it works. You just have to relink the tables. The problem comes up when we put the files in Sharepoint. We generate a Sharepoint shortcut and try to use that as the location of the tables and Access doesn't like the link. Not sure why, probably the format.
We were able to make the application function for one user by making a Onedrive shortcut to the folder containing the files. The problem with this is it is a cached copy. So the concern is if more than one user each have their own local copy, the database could get corrupted when it synchs. In testing, it appears that Sharepoint creates a second copy of the database to protect the file integrity. So maybe the files are safe, but the app doesn't work.
Everything I find on running Access databases off Sharepoint talks about how to design the application, so not applicable to my situation.
Short of creating a VM in the cloud to run the application, is there another way to make this work?
We have tried moving the application files to other locations on the network or local machine and it works. You just have to relink the tables. The problem comes up when we put the files in Sharepoint. We generate a Sharepoint shortcut and try to use that as the location of the tables and Access doesn't like the link. Not sure why, probably the format.
We were able to make the application function for one user by making a Onedrive shortcut to the folder containing the files. The problem with this is it is a cached copy. So the concern is if more than one user each have their own local copy, the database could get corrupted when it synchs. In testing, it appears that Sharepoint creates a second copy of the database to protect the file integrity. So maybe the files are safe, but the app doesn't work.
Everything I find on running Access databases off Sharepoint talks about how to design the application, so not applicable to my situation.
Short of creating a VM in the cloud to run the application, is there another way to make this work?
ASKER
Thanks Jim. Don't get me wrong, it "works" with the application shared from Sharepoint, but not without the risks I mentioned. Understanding there is a difference of course between "works" and "supported". So far it is the only thing holding up getting this department's entire infrastructure to the cloud.
By moving it a VM, I mean setting up a windows workstation running in the could and putting the application on it. Haven't tested this idea yet, but theoretically if it works on a local workstation, I don't see why it wouldn't work on a VM?
By moving it a VM, I mean setting up a windows workstation running in the could and putting the application on it. Haven't tested this idea yet, but theoretically if it works on a local workstation, I don't see why it wouldn't work on a VM?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I second Jim's statements. I'm dealing with exactly this scenario with a client and now they are in a mess. SharePoint has spawned multiple copies of their database because of multi user usage and now the data is scattered, even stopped synching for some users. A nightmare to try and clean up! Don't do it.
If the db has small tables then SharePoint lists may work, but the 5000 record limit is a major issues for most real database systems.
Another option is to migrate to Azure SQL and connect to it.
CITRIX could be an option through a web portal or VPN connection.
If the db has small tables then SharePoint lists may work, but the 5000 record limit is a major issues for most real database systems.
Another option is to migrate to Azure SQL and connect to it.
CITRIX could be an option through a web portal or VPN connection.
The cloud VM works just fine...RDP it or even better make it a RemoteApp and it would seem almost transparent to the End User ...like its local.
BUT it doesn't mean that you have a Cloud-Version of your Access application....just instead having it stored locally it run from somewhere in the world.
Cloud-Version Access is only achieved via having a 3rd party Database Engine as BE and via ODBC communicate with it.
BUT it doesn't mean that you have a Cloud-Version of your Access application....just instead having it stored locally it run from somewhere in the world.
Cloud-Version Access is only achieved via having a 3rd party Database Engine as BE and via ODBC communicate with it.
<<Short of creating a VM in the cloud to run the application, is there another way to make this work? >>
No, not with an Access DB for the back end.
Jim.