We started out with the same database. How do we synchronize chan

[Wil]

Greetings:

Two of us. in two different cities, have modified and must continue to
modify the same database.

We now have two modified versions, with new records in both that we have to
combine. Once a month we will have to get together and synchronize our new
and ole modified records.

1. What is the best way to synchronize, and what can we do in the future to
simplify matters please?

2. Does Access make it easy to decipher which updates to keep?

Would you be kind enough to teach a newbie? Thanks.


And on another note,

3. Office had a "briefcase" in the past which allowed an operator to do
some work from home and synchronize at the office. Would this help?

4. Have any of you used an internet based database, only modifiable by one
user at a time?


Any suggestion would help. Thanks.


Wil

 

[Wayne-I-M]

Hi

It is relatively simple to update tables with new data.
BUT
Most people use a unique identifier to locate new records. This is where
you problem may lie.

eg.
Database 1
TblNames
ID 1 John
ID 2 Sally
ID 3 Jim

eg
Database 2
TblNames
ID 4 Larry
ID 5 Keith
ID 7 Sally

In this case you just run an update query on the table from 2 to 1 using the
max of tblNames in 1 as the criteria. Note that in the above example ID 2
and 7 have the same name but as you are using the primary field as the
criteria this does not matter.

But if you have tblName in DB 1 as above and
Database 2
TblNames
ID 2 Larry
ID 3 Keith
ID 4 Sally

In this case only ID 4 would be appended.

I think you may be able to update the table (2 to 1) would you need to use
"almost" (?) the complete record as the criteria to ensure you don't miss any
new records from 2 into 1

If you need more info on using the append method post back and someone will
be able to help (but add more details of the lay out of your application)

 

[Wayne-I-M]

Sorry forgot to add

1. What is the best way to synchronize, and what can we do in the future to
simplify matters please?

Create a copy of the tables in one DB and rename them (maybe add a 1 or 2 or
copy to thye names)

Then append this info into the main tables in the other DB

Oh, we have lots on out-of-office lap tops that I append any info from them
onto the main DB quite a few times a month, so it's not too difficult to set
up

 

[Arvin Meyer [MVP]]

Replication is available in the MDB format, and it has an interface in
versions 2003 and earlier. I've never used Briefcase, and not only has it
been deprecated (as has Replication in the newest versions) but there has
never been a great deal of success with that application.

There is a replication FAQ still available:

http://support.microsoft.com/kb/282977/en-us

 

[David W. Fenton]

Greetings:

Answered in microsoft.public.access.replication.

Double posting is really stupid and makes me want to retract my
answer.

 

[David W. Fenton]

Replication is available in the MDB format, and it has an
interface in versions 2003 and earlier. I've never used Briefcase,
and not only has it been deprecated (as has Replication in the
newest versions) but there has never been a great deal of success
with that application.

There is a replication FAQ still available:

http://support.microsoft.com/kb/282977/en-us

http://dfenton.com/DFA/Replication

http://dfenton.com/DFA/Replication/index.php?title=Replication_Myths

 

[Arvin Meyer [MVP]]

Yes, thanks, David. I will add those links to my future replies.

 

[David W. Fenton]

Yes, thanks, David. I will add those links to my future replies.

The "Myths" article is not so important generally, but it discusses
Briefcase replication, and since that's been brought up here, I
thought it should be cited directly.