Answered by:
Desktop Application/Webapp/Sharepoint list to share among users

Question
-
I have to decide how to best share an Access application with someone else who does not work for our company. Until now, all I have created desktop apps and shared them internally. I know I can create a WebApp, but the customization of the forms is limited. Being able to create intelligent and customized forms is very important in this application. I saw where you can create your tables and link them to Sharepoint lists. I have a subscription to Sharepoint and could get the same for the individual i need to share the application with. If I understand how this works is that the data, forms and reports will reside on the user's hard drive. The data in the tables will also be linked to lists in the Sharepoint cloud. This will allow this other individual to have a duplicate copy of the database on his end and add and edit records but still have the very customized forms and reports that exist in the desktop application. I am trying to decide which is my best option in this situation. Any advice you have would be much appreciated. I am using Access 2016 and the Sharepoint I have is through Office 365 with access services.
thanks.
Friday, October 7, 2016 3:14 PM
Answers
-
Hi,
If you don't have a dedicated Server for sharing the database with the other user, then using SharePoint (O365) would not be a bad choice. However, it won't be the same as what you're used to with desktop apps. For instance, the number of records you store in SharePoint will affect its performance. If you have less than 5000 records, you will be okay.
One good thing you mentioned about using SharePoint is the ability to work offline. SharePoint will cache the data on the user's local hard drive and automatically synch up with the server when a connection is available.
Hope it helps...
- Marked as answer by jdmcleod Friday, October 7, 2016 3:36 PM
Friday, October 7, 2016 3:19 PM -
Hi,
1. Yes, you would continue to develop using Desktop Access and link the tables to SharePoint Lists. The other user will then use the same front end application, you developed, to work with the same data in SharePoint.
2. No, SharePoint will require any user connecting to the data to have an account and permission. So, even though the other user will only use the Access front end application, he or she is still using SharePoint in the background, because SharePoint will ask them to log in or provide their credentials.
Hope it helps...
- Marked as answer by jdmcleod Friday, October 7, 2016 4:05 PM
Friday, October 7, 2016 3:45 PM
All replies
-
Hi,
If you don't have a dedicated Server for sharing the database with the other user, then using SharePoint (O365) would not be a bad choice. However, it won't be the same as what you're used to with desktop apps. For instance, the number of records you store in SharePoint will affect its performance. If you have less than 5000 records, you will be okay.
One good thing you mentioned about using SharePoint is the ability to work offline. SharePoint will cache the data on the user's local hard drive and automatically synch up with the server when a connection is available.
Hope it helps...
- Marked as answer by jdmcleod Friday, October 7, 2016 3:36 PM
Friday, October 7, 2016 3:19 PM -
Ok, thanks. Tow followup questions:
- So if I go the route of using the Sharepoint lists, would i just go about building my application in the desktop environment as I normally would and mapping the tables to Sharepoint as i go?
- I guess the other user will really not even use the Sharepoint lists? Wouldn't he just work in the desktop application with a link to the Sharepoint tables?
Thanks again for your earlier response.
Friday, October 7, 2016 3:39 PM -
Hi,
1. Yes, you would continue to develop using Desktop Access and link the tables to SharePoint Lists. The other user will then use the same front end application, you developed, to work with the same data in SharePoint.
2. No, SharePoint will require any user connecting to the data to have an account and permission. So, even though the other user will only use the Access front end application, he or she is still using SharePoint in the background, because SharePoint will ask them to log in or provide their credentials.
Hope it helps...
- Marked as answer by jdmcleod Friday, October 7, 2016 4:05 PM
Friday, October 7, 2016 3:45 PM