chuckcoleman
Registered User.
- Local time
- Today, 18:26
- Joined
- Aug 20, 2010
- Messages
- 377
I built an application for a client that had three remote sites. The Access front-end database runs on the local machines, (main location and three remote offices), and the data in the back-end is on a SharePoint list. Now, when I need to do updates on the clients front-ends, I'm wondering how best to do that. In the past in a non-SharePoint application where the customer was all in the same location and had a server, I would copy a new front-end to the server, to a specific folder, and I provided each client a little batch file that they executed that did an XCopy from the server to their local machine. Then they had a new client front-end.
This is my first experience with SharePoint and I'm wondering how I can distribute a new version of the front-end to the "HQ" location clients as well as the three remotes? It would seem to me that SharePoint has a ton of features and potentially one of them could be used. A side concern is the data in the client's front-end SharePoint tables aren't going to be in sync with the real data on the SharePoint site and I'm nervous about deleting some SharePoint site data when the front-end syncs with the SharePoint back-end.
Any advice would be appreciated. Any links to articles on this subject would also be helpful.
Thanks,
Chuck
This is my first experience with SharePoint and I'm wondering how I can distribute a new version of the front-end to the "HQ" location clients as well as the three remotes? It would seem to me that SharePoint has a ton of features and potentially one of them could be used. A side concern is the data in the client's front-end SharePoint tables aren't going to be in sync with the real data on the SharePoint site and I'm nervous about deleting some SharePoint site data when the front-end syncs with the SharePoint back-end.
Any advice would be appreciated. Any links to articles on this subject would also be helpful.
Thanks,
Chuck