Absolutely give each user their own local copy of the front end. For starters, there's a lot less lag when working with a local file instead of one on the network, but even more importantly is this: due to how Access processes things, having more than one person in the same front end at the same time causes an ever-increasing chance of fatal corruption. It changes from 'if' a file will be corrupted to 'when'.
Okay, they're using VM's, so local is out, but they should still get their own copies of the front end.
As to updating, there are several ways you can do this:
- You can use a launcher program that checks for updates and downloads if necessary, then launches the app.
- You can put code in the front end itself to check for and apply updates automatically.
- You can point their shortcuts to a batch file that downloads the most recent copy every time they start the app.
I'm sure there are others, too. My suggestion would be to search this forum for threads on automatically updating front ends - this is a fairly common question, so you'll find a lot of hits and a lot of information.