Splitting a Database

[Gail]

Is there a web site that can give me a lot of details on
how to split a database (Access 2000), how the process
actually works and everything that I should know about a
split database.

I have been told that for a database that has multiple
users, I need to split the database in order to be able to
work on the design of the database while others are using
it to enter data.

I don't know the first thing on how the front-end or back-
end work, who is supposed to use what, if there is
anything I need to do to set this up other than to use the
wizard to split it. Do I just set up a shortcut directed
to the database on the server for the users (and which
one - the front-end or back-end.) Is the original
database the front end? .... etc, etc, etc. I have lots
and lots of questions on how to do all of this.

Any information I can find that will give me specific
instructions or details on this process is greatly
appreciated.

Whenever I need to do any design work (which is quite
often right now), I have to have all users close the
database until I am finished. This is very inconvient
since we are in the beginning stages of desgning this new
database and it is already being used regularly by 2
people in the dept.

Thank you very much in advance for any help on this topic.
Gail

 

[Douglas J. Steele]

See whether what Tony Toews has at
http://www.granite.ab.ca/access/splitapp/index.htm is sufficient for your
needs.

 

[tina]

generally speaking, when a db will be used by multiple
users, it should be split into a backend db which holds
all the data tables, and a frontend db which holds all the
the other database objects. the backend db is placed on
the server (usually with a db password that only the db
developer/administrator knows), in a folder that all users
have read/write permissions for. the backend db's tables
are then linked to the frontend db master, and a copy of
the frontend db is placed on each user's pc. the frontend
db should NOT be placed on the server and accessed by
multiple users!
once you create that setup, you can continue developing
the master frontend db on your own pc's hard drive
(remember to always keep a "clean" copy of the master db,
as a backup). to deploy an enhanced version of the
frontend db to your users, overwrite the frontend db
sitting on each user's hard drive with a copy of the new
frontend db.
you can use the db splitter wizard in Access, or do it
yourself. just make 2 copies of your complete db. remove
all the tables from one copy (now the frontend), and
remove all the other db objects from the other (now the
backend).

hth