The first thing you must do is to "split" the database into a back-end
(consisting of just the data tables) and a front-end containing everything
else. This can be done from the Database Tools tab, Move Database group,
Access Database button.
Then you need to identify a suitable location for the back-end. It needs to
be on a file server or other computer where all users can access it and have
sufficient privileges to update it, and where it will be regularly backed
up.
Then you need to prepare to deploy the front-end. All computers where it
will run must (i) have Access 2007 installed (full version or run-time
version) and (ii) be able to access the back-end file using *wired* LAN
connections (you cannot reliably run an Access application over a WAN or a
wireless network connection).
You now need to deploy the front-end file by (i) re-linking the tables to
the back-end at it's chosen location, using the Linked Table Manager and
(ii) copying it to each user's computer, and making it accessible to them
(usually by means of a desktop shortcut). You have two basic options for
doing this: (i) you can do it manually as a one-off exercise or (ii) you can
build a routine which automtically creates a "fresh" copy of the file every
time the user runs the system (I find that vbscript is very good for this).
Option (i) has the advantage that any layout and appearance changes the user
makes at runtime are retained, but the disadvantage that the file will be
prone to bloat and corruption, and will need regular compacting and possibly
occasional replacement if it gets corrupted. Option (ii) has the advantages
that the file will not suffer from corruption or bloat, and deploying
updated versions is easy, but the disadvantage that any runtime changes made
by the user will be lost each time the application is re-started.
