7
Problem:
In our office we have an Access customer database that is about 20MB big. People mostly use it from within the office's LAN, but some other team members are external and they currently have the following workflow:
- Ask somebody in the office to upload the file to an FTP server
- Tell others to stop making changes in the database
- Download the database, commit changes
- Upload it to the FTP server and tell the office that it's usable again
Question:
What is the easiest way to allow those people to make changes to that database without needing to resort to the methods above?
There should be no need for real "live" and collaborative editing, but the process should be fairly easy to learn for "normal" PC users and involve as little effort as possible for me on the developer/sysadmin side.
+1, I never thought about the first solution, but it seems like the best fallback if there are no resources available to migrate the DB or buy/setup Sharepoint. – slhck – 2011-05-27T08:27:28.517
Note that Sharepoint is relatively expensive. – Tony Toews – 2011-06-10T03:48:11.407
Yeah, that's my main concern, although I'm not the one with the budget, only the guy who has to implement it. Actually I just convinced them just to go for the RDP solution. – slhck – 2011-06-10T10:49:57.790