By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,982 Members | 1,919 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,982 IT Pros & Developers. It's quick & easy.

Master database backend (20 offices) Please help!

P: n/a
I have a dilemma. I have 20 branch offices that need to be able to
upload their unique copy of all their backend tables to a master
database at a corporate office. I really need only a copy of those new
records, deleted records , or changed records (but I guess exporting
all the data would not be a problem, not very big tables). Can I write
a query that updates the master database tables at corporate and have
that query launched on demand or using AutoExec when they open the
client frontends at the branches? The resulting corporate master
backend would have data currrent to whenever the various updates occur.
My only other thought is to have what at most will be 30 concurrnet
users accessing not "child" database backends, but the actual master
backend. The way I would in both cases have each branch see only their
data would be a branch identifying field which would, by query on this
field, load their unique data.....

Any pointers would help... Thanks Dave

Oct 20 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Parasyke wrote:
I have a dilemma.
Yes, you do.

I have 20 branch offices that need to be able to
upload their unique copy of all their backend tables to a master
database at a corporate office. I really need only a copy of those new
records, deleted records , or changed records (but I guess exporting
all the data would not be a problem, not very big tables).
How would you send the data? Over a WAN where Corporate could connect
to the database or via an email?

Can I write
a query that updates the master database tables at corporate and have
that query launched on demand or using AutoExec when they open the
client frontends at the branches? The resulting corporate master
backend would have data currrent to whenever the various updates occur.
What is your delivery/update method/medium?
My only other thought is to have what at most will be 30 concurrnet
users accessing not "child" database backends, but the actual master
backend. The way I would in both cases have each branch see only their
data would be a branch identifying field which would, by query on this
field, load their unique data.....

Any pointers would help... Thanks Dave
There is replication. You might want to read up on it, see if that
would work.

Does corporate really need all of the detail, the nuts and bolts inside
each mdb or could it subsist on consolidated detail passed to it for
reports? I would think branches take care of detail, corporate takes
care of the overall picture...summarized data.
>
Oct 20 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.