Yes, the database should be split. The frontend should be set so that EACH
user has a copy on their machine. See here for more about splitting:
http://www.members.shaw.ca/AlbertKallal/Articles/split/
And if you use my Frontend Auto Update Enabling tool, it will enable you to
do auto updates of your frontends. Yes, the first distribution you will need
to get it to people somehow and that is in your court. But, if you have
enabled auto updating, then you can just go into your master file on the
network, make your changes, change the version number in two tables (one in
the frontend and one in the frontend that is linked to the backend), then
when your users open their frontend and the version numbers don't match it
will tell them that their frontend is out-of-date and it will close, delete
the old file, copy the new file, and then reopen for them automatically.
I had to create this for a big healthcare provider I worked for which
originally had over 100 users using a single mdb frontend on the server and
they wondered why it crashed each week, or several times each week. So, once
we implemented this and moved to frontends on each user's machine, they never
had a corruption issue again as long as I was there.
You can download it here:
http://www.btabdevelopment.com/main/MyFreeAccessTools/tabid/78/Default.aspx
--
Bob Larson
Access MVP
Access World Forums Administrator
Utter Access VIP
Tutorials at
http://www.btabdevelopment.com
__________________________________