T
tina
Access 2000 has a Database Splitter, under Tools, Database
Utilites on the menu bar. i don't recall if 97 has
similar, and i'm guessing that 2002 does.
you can also do it manually. i usually create a new blank
database as a base file, and export the tables and
relationships into it from the original db. then i open
the original db, delete the relationships and tables, and
link the tables from the base file back into the original -
which is now my frontend db. in most situations, i put a
copy of the frontend db on each user's hard drive - and
keep the base file on the network.
you can make changes to a copy of the frontend db, then
deploy it to the users whenever you want. recommend you
link the frontend copy to a copy of the base file on your
hard drive while you're working on it, not to the live
base file on the network.
shouldn't be a problem unless your changes to the frontend
require concurrent changes to the base file's tables
and/or relationships.
hth
Utilites on the menu bar. i don't recall if 97 has
similar, and i'm guessing that 2002 does.
you can also do it manually. i usually create a new blank
database as a base file, and export the tables and
relationships into it from the original db. then i open
the original db, delete the relationships and tables, and
link the tables from the base file back into the original -
which is now my frontend db. in most situations, i put a
copy of the frontend db on each user's hard drive - and
keep the base file on the network.
you can make changes to a copy of the frontend db, then
deploy it to the users whenever you want. recommend you
link the frontend copy to a copy of the base file on your
hard drive while you're working on it, not to the live
base file on the network.
shouldn't be a problem unless your changes to the frontend
require concurrent changes to the base file's tables
and/or relationships.
hth