A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

one or many db's



 
 
Thread Tools Display Modes
  #1  
Old January 12th, 2005, 08:17 PM
owilson
external usenet poster
 
Posts: n/a
Default one or many db's

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
  #2  
Old January 12th, 2005, 11:04 PM
Lynn Trapp
external usenet poster
 
Posts: n/a
Default

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.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdeisgns.com/Security.htm


"owilson" wrote in message
...
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



  #3  
Old January 12th, 2005, 11:46 PM
John Vinson
external usenet poster
 
Posts: n/a
Default

On Wed, 12 Jan 2005 12:17:50 -0800, "owilson"
wrote:

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]
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 06:59 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.