View Single Post
  #5  
Old April 23rd, 2010, 06:01 PM posted to microsoft.public.access.tablesdbdesign
Rlong via AccessMonster.com
external usenet poster
 
Posts: 7
Default Design for future merging

Thanks for the continued input. The different locations are simply entering
new data, and won't need to see or edit data from the other locations or the
base location. After 3 months of data entry, each offsite database will
ideally be brought into the base database and use at other locations will be
discontinued.

Thanks.


Fred wrote:
I think that you will need to be thinking about your "data" mission and data
specifics with all of these databases as a being the core of answering this
question. (or maybe you have already and didn't describe it to us.)

For example:

Are these different locations editing records that are for the same entity
(e.g. updating data for a particular person at multiple locations)

Are these different locations just adding records, or are they editing
existing records? If it's the latter, what will they be looking at to edit?


Etc.

Once you get those kinds of things decided, then those decision should how
you created your structure.

Replication was, in essence, to manage having, (and, more to the point,
editing on) multiple copies of the same database.


--
Message posted via http://www.accessmonster.com