Distributing a Db for use and updating a main Db when they are returned every month

  • Thread starter Thread starter Andrew
  • Start date Start date
A

Andrew

I am developing a database that will be distributed to multiple (10+)
offices. I would like to be able to have them email their versions of the
database back to me every month and update our main database with the new
data. The records that have had changes in the remote databasea since the
last update needs to be changed on the main Db as well as adding the new
records. Is there a standard way of doing this and is there any websites
out there with information that may be helpful.
 
Replication is the first thing that comes to mind, but it is not for the
faint of heart and if not properly setup can be more trouble than it's
worth. There are a couple of newsgroups devoted to it, and of course MSDN,
the Developer's Handbook, etc etc ...
 
Read up your Access books / Access Help on "Replication"
and "Splitting Database (into Front-End and Back-End)"
before you proceed.

HTH
Van T. Dinh
MVP (Access)
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Opening a db 2
Migrate updates from developement to production DB 2
PLS HELP - Access DB Has slowed right down 5
Attachment field question and db size question 5
Attachment field question and db size question 3
Get internet leads into main DB 1
Access 2007 Split Assets db, issue moving to new directory 0
An Archive Database 4

Back
Top