Advantage to Breaking-Up database to Front end & Back end ???

[Will]

We will put our data base in a shared folder on an unused computer on our
peer-to-peer network.

Normally only 2 people will be using it.

One day maybe 3 or 4 people will be using it.

I can just put the entire Access database in the shared folder along with
all the tables, queries & Forms and we can use it...

Or I can split it up so only the tables are in the shared folder and each
user has an Access file with only the queries and forms on their individual
computer... such queries & forms linked to the tables on the shared machine.

Is there an advantage one way or the other for splitting it up? The
dis-advantage is that each time we want to create a new query or form we
have to go to each computer and do it... that is a lots of maintance.

thanks for any help on this.

Will

 

[Albert D.Kallal]

You are right about the disadvantage.

However, you need a way to test, and work on this query BEFORE you release
it anyway.

To be honest, you might get away with just two people.

You can read as to what, why, and the advantages of splitting here:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

The above also has a link to a solution to update the database that resides
on each computer...

 

[Douglas J Steele]

You should definitely split it such that only the tables are in the shared
folder, and each user has his/her own copy of the front-end on their
individual computer.

To help with the redistribution after making changes, check out the free
Auto FE Updater Tony Toews has at http://www.granite.ab.ca/access/autofe.htm