"Roger Carlson" wrote:

Sorry for the OT in the last post. I shall try to make amends...

The FE can be installed on each workstation OR accessed from a single file
on a server OR you can have a directory on the server for each user and have
a separate FE in each. I have done all of these. There are advantages and
disadvantages to each.

* FE on the Server:
- Advantage: one copy to maintain (you should do your development in an
off-line copy and copy it over the network version)
- Disadvantages: 1) it is more susceptible to corruption. 2) performance
suffers some. 3) you have to kick everyone out of the application in order
to copy your revised version over it. 4) may have multi-user problems if
you create temporary tables and such.

* Separate FE in separated directories on the server:
- Advantage: 1) no multi-user issues. 2) less danger of corruption
- Disadvantages: 1) performance can suffer. 2) you have to copy your
development copy over each individual copy. 3) you have to kick the user
out in order to over-write it.

* FE on each workstation:
- Advantages: 1) no multi-user issues. 2) less danger of corruption. 3)
improved performance (over the other options)
- Disadvantages: 1) you have to manage updating the FE on separate systems.

The normal recommendation is to put the FE on each workstation and I
generally agree with that. This does require some sort of update routine
when you change the application. On my website
(www.rogersaccesslibrary.com) there is a small sample database called
"KeepingDatabasesInSync2.mdb" that does this. Tony Toews has a utility
called "Auto FE Updater"
(http://www.granite.ab.ca/access/downloadsindex.htm) that also does this.

--
--Roger Carlson
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/...UBED1=ACCESS-L

"HelenJ" wrote in message
...
I'm not sure if I should start a new thread here - but the last one went a
bit off topic so...

OK I have now split my database, (well only on my system) - but doesn't
this
now mean more work for me? from the articals that I read I got the
impression that the front end has to be "installed" on each users PC - so
won't that mean when I develop new reports forms etc I will have to copy
it
into multiple database front ends? (currently only 2 but will become more)

Or do I install the front end on the server so the users open it from
there?

Sorry I'm slightly confused and all the articles that I read seem to only
ever give part of the picture...



Thanks for all your helpful advice and don't worry about the "OT" - when
developing in Access I think you need a sense of humour :-)

Just at the moment I feel as though I am standing on the edge of a large pit
full of all kinds of "stuff" about Access that I really don't understand - at
the moment I can still breath - but I haven't really taken the plunge (I did
make a change to my references library yesterday - eek!)

Is there any book series of books that any of you could recommend - I have
an Access Bible and even a VAB for Dummies - both of which have helped - but
now I feel I need something that bridges the gap between what is, if you like
"inside" Access eg tables and even a little code - and the link to the
outside world - I don't even really know what it is I am looking for - but
any advice gratefully recieved - this Discussion group really is a life line!