Updating Tables

[mel]

I just started working on a side job. The problem is
that each employee is using a copy of the access 2000 db
and now I have to update the master copy tables with the
changes they have made. It isn't just an append because
this is updating existing rows that were already in each
of their copies of the db. Any help is appreciated.

Melissa

 

[Bruce M. Thompson]

I just started working on a side job. The problem is

that each employee is using a copy of the access 2000 db
and now I have to update the master copy tables with the
changes they have made. It isn't just an append because
this is updating existing rows that were already in each
of their copies of the db. Any help is appreciated.

Split the database and update only the front-end (data will then reside in
back-end).

Splitting your Microsoft Access MDB into a front end and back end
http://www.granite.ab.ca/access/splitapp.htm

 

[John Nurick]

Hi Mel,

If all the computers are on the same local network, the thing to do is
to have all the employees share the same data. Split the database (look
it up in Help) so the data is in one "back end" mdb file in a shared
folder, while each computer has its own copy of the "front end"
containing the forms, queries, etc.

If the computers aren't always connected to the network but can connect
at least occasionally (e.g. via a WAN or VPN), Access's Replication
feature is designed for the job. Read up on it carefully before
implementing it.

If you're working with multiple stand-alone computers, things get
complicated.

I just started working on a side job. The problem is
that each employee is using a copy of the access 2000 db
and now I have to update the master copy tables with the
changes they have made. It isn't just an append because
this is updating existing rows that were already in each
of their copies of the db. Any help is appreciated.

Melissa

John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.