Split Database Question...

[Paul]

I split an Access database into front-end and back-end and saved them into a
location that cab ne accessed from a network, at the server. The front end
of the application can be accessed by up to 20 people in a time. I created a
link to the front-end applicatrion on the user desktop. Should I worry if
more than 1 person logged on to it and it will corrupt the front-end
application or the data in the back-end? I do have a back-up for both the
front-end and back-end just in case. Thanks.

 

[Allen Browne]

The whole idea of splitting the application is so that everyone has their
own copy of the front end instead of all trying to run the one file.

For best results, put a copy of the front end locally on each user's
workstation. If that is undesirable, then put a copy in each user's
workspace on the server so at least they are running independent copies.

 

[Paul]

I agree totally but if I make a change to the front end then I have to
update all other copies whick link to the user's workstation. If I deploy
only one copy of the front end and have it link to all the users, I only
need to update one front end. Thanks.

 

[John Spencer (MVP)]

Check out the following url

http://www.granite.ab.ca/access/autofe/faq.htm

This utility will allow you to maintain a master copy on the server that will be
copied to the user workstations as needed.