Database sharing issues ...

[m.cringle]

Looking for a little honest advice.

I am about to share my database accross the company (approx 40/50
people). I have split the database up into front and back-ends and have
applied user-level security.

My original idea was to install a link on each persons pc which will
open a shared front-end on the network (dedicated link required due to
user-level security). However, now i'm starting to wonder whether it
would be better / more stable to install a seperate front-end on each
pc which all link to the same back-end (which will be stored on the
network).

Only a few people will have ad, edit & delete permissions; with the
majority having read-only permissions.

This will be more work and difficult to arrange so i only want to do it
this way if it will be necessary - what do you think??

 

[Jeff Boyce]

Take a scan through the tablesdbdesign newsgroup. You'll find a strong
consensus there that it is preferable to put a copy of the front-end on each
PC, rather than have multiple folks sharing a single front-end.

Yes, it takes a bit more work to roll out changes, but it seems to greatly
reduce the chances of getting your front-end or your back-end corrupted when
a well-intentioned user turns off his PC in mid-application...

--
Regards

Jeff Boyce
Microsoft Office/Access MVP


Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/

Microsoft Registered Partner
https://partner.microsoft.com/

 

[m.cringle]

That's just the info I needed - thanks Jeff

Take a scan through the tablesdbdesign newsgroup. You'll find a strong
consensus there that it is preferable to put a copy of the front-end on each
PC, rather than have multiple folks sharing a single front-end.

Yes, it takes a bit more work to roll out changes, but it seems to greatly
reduce the chances of getting your front-end or your back-end corrupted when
a well-intentioned user turns off his PC in mid-application...

--
Regards

Jeff Boyce
Microsoft Office/Access MVP


Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/

Microsoft Registered Partner
https://partner.microsoft.com/

 

[Guest]

I use the Autoexec.bat file or, with the network administrators help, a
startup batch file to copy a fresh FE file to the user computers during
boot-up. That way I put the latest FE out on the network where the script
looks to copy the file and the update is done. Also if the FE ever gets
corrupt, a reboot of the computer fixes it. Downsides include a few extra
seconds when booting up and you need to remind the users to reboot or shut
down their computers every once in a while. Drive mapping can be a problem
both in copying the file and relinking the tables if you don't use UNCs or
the network doesn't have standardized drive letters.

 

[Larry Daugherty]

FWIW you might also browse Tony Toews' site for information he has
created and/or accumulated and presents there. If you aren't already
aware of it look for his Front End Updater.

HTH