one or many db's

[owilson]

Hi,

Need a little advice here. I have a database that is
designed to track several projects at once. It will
eventually be used by different people on different
computers simultaneously.

Is it better to have a databse copy on each machine that
updates a main db or to have one db with links to each
machine?

All the data from all projects will be compiled to give an
overview of the companies project status as well as the
status of each project.

TIA

Owen

 

[Lynn Trapp]

If everybody is in one location and are all have access to the same server,
then it's best to just use one database. If, on the other hand, you have
users spread out in many locations, you may want to look into using Access
replication. There is a newsgroup dedicated to replication --
microsoft.public.access.replication.

 

[John Vinson]

Hi,

Need a little advice here. I have a database that is
designed to track several projects at once. It will
eventually be used by different people on different
computers simultaneously.

Is it better to have a databse copy on each machine that
updates a main db or to have one db with links to each
machine?

Neither.

Use a "Split" database. Have a "backend" database, containing only the
Tables, on a shared server; and a "frontend" database, containing the
Forms, Queries, Reports, etc., with links to the tables in the
backend, on each machine.

There's a Database Splitter Wizard under Tools... Database Utilities
to set this up for you.

John W. Vinson[MVP]