Sharing MS Access database (2016 Version) (1 Viewer)

Rakesh935

Registered User.
Local time
Today, 21:24
Joined
Oct 14, 2012
Messages
71
Hi Guys,

I have developed an MS Access database (2016 Version) consisting of tables, sqls, vba and macros for my team. The next challenge is, my team is consisting of about 40 associates and they need to update this database on a daily basis.

So far, my thought process is to split the database, keep the primary file in the shared drive and share the front end through email so that all of my associates have their own front end copy.

Please advise me if my approach is right and if not, then what could be an alternative best method to make this file shared for multiple users.

Thanks in advance for all your suggestions.

Regards,
Rakesh
 

GinaWhipp

AWF VIP
Local time
Today, 11:54
Joined
Jun 21, 2011
Messages
5,901
Yep, backend on Server and frontend to individual Uses is the only way. For some help have a look at...


http://www.kallal.ca/Articles/split/index.htm

http://allenbrowne.com/ser-01.html

http://www.utteraccess.com/wiki/index.php/Sharing


You may also want to take a look at MVP Tom Wickerath's article…

http://www.accessmvp.com:80/Twickerath/articles/multiuser.htm


To handle the update of multiple front ends see…

http://www.autofeupdater.com/
https://regina-whipp.com/blog/?p=184
http://www.btabdevelopment.com/ts/freetools
 
Last edited:

isladogs

MVP / VIP
Local time
Today, 15:54
Joined
Jan 14, 2017
Messages
18,186
I haven't checked Gina's links so apologies if this is repeating what those say.

To add to Gina's comments, make sure your associates do not try to run the front end from the email attachment. It won't work properly and could cause issues. It needs to be installed to their hard drive.

A better method for distribution would be to have a network folder where the latest copy of the FE is stored. Next get IT support to copy the file itself and a desktop shortcut to the hard drive of each user.

Do NOT give users write permission to that folder to ensure the FE isn't run from the network.

When the FE is opened, code is used to check if a newer version exists on the network. If so, that is downloaded and used to overwrite the old version. Otherwise the file opens normally.
Look up FE Updater in this forum and online. There are many free examples including the links given by Gina
 

Rakesh935

Registered User.
Local time
Today, 21:24
Joined
Oct 14, 2012
Messages
71
Thanks Gina and Ridders for your help ....

@ ridders - Just 1 question out of curiosity if I do not give users, write permission to that folder located in shared drive then would my users be able to update or add a new record to database through the FE?

Thanks,
Rakesh
 

isladogs

MVP / VIP
Local time
Today, 15:54
Joined
Jan 14, 2017
Messages
18,186
Thanks Gina and Ridders for your help ....

@ ridders - Just 1 question out of curiosity if I do not give users, write permission to that folder located in shared drive then would my users be able to update or add a new record to database through the FE?

Thanks,
Rakesh

I was talking about the folder containing the latest version of the FE.
The idea is to prevent anyone opening the FE from the shared drive.

Obviously the BE file needs to be editable (via the FE).
 

psyc0tic1

Access Moron
Local time
Today, 10:54
Joined
Jul 10, 2017
Messages
360
If any of my experiences on this matter mean anything... the folder where the back-end is stored... the users will need READ and WRITE access to that folder or they will not be able to access it from their front-end
 

isladogs

MVP / VIP
Local time
Today, 15:54
Joined
Jan 14, 2017
Messages
18,186
Thanks for clarifying the point I was making. Much clearer now.
 

Users who are viewing this thread

Top Bottom