Synchronize databases

[Guest]

Windows 2000/XP
Access 2000/2003

I have set up a database and replicated the backend. Everything is working
well when I manually synchronize. I would like to set up a process that
automatically syncronizes the two databases every 2 hours using a macro or
code? Any ideas?

Thanks in advance

 

[Guest]

Hi Jim,

This is covered starting on page 405 of Access 2002 Enterprise Developer's
Handbook, written by Paul Litwin, Ken Getz and Mike Gunderloy (Sybex). They
state that if you have the Developer's Edition for Access 2002, you can use
Replication Manager to "Create a regular synchronization schedule for a
replica set."

I don't know if this is supported in Access 2000, since my copy of the book
is the 2002 edition.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[David W. Fenton]

This is covered starting on page 405 of Access 2002 Enterprise
Developer's Handbook, written by Paul Litwin, Ken Getz and Mike
Gunderloy (Sybex). They state that if you have the Developer's
Edition for Access 2002, you can use Replication Manager to
"Create a regular synchronization schedule for a replica set."

I don't know if this is supported in Access 2000, since my copy of
the book is the 2002 edition.

I don't know exactly which methods are being recommended in the 2002
book, but the 2000 edition offers explanations of how to schedule
with Replication Manager and how to do it with JRO.

The latter is bloody stupid. of course, as the same thing can just
as easily be done with DAO (since the example uses direct
replication).

The two methods are:

1. using the synchronizer, set up a schedule. This can be done with
ReplMan or with the TSI Synchronizer (see http://trigeminal.com to
download it).

2. using a form with a timer to do the synch. If you use JRO you can
use direct or indirect (but for indirect you have to have the
synchronizer running, and controlling that is easier with the TSI
Synchronizer than it is with JRO), if you use DAO you can only use
direct.

Given that a direct synch is OK for the original poster, DAO would
be just fine.

The more I use Jet 4 replication, the more I consider JRO to be
completely irrelevant and useless. Too bad the people writing all
the documentation were not smart enough to figure that out.

 

[dbahooker]

DAO?

go and play with your own time machine; ****er

MDB and DAO are obsolete; but I will not let you preach this DAO crap

use SQL Server; it's 100 times easier to manage and it's reliable

-Aaron

 

[Natalie_Allen]

Could you possible share this code you wrote for synching through a
form? Thanks!

 

[Guest]

Here is the cod I used behind the for that loads when the DB is opened. I do
not want it to run on Saturday or Sunday

Private Sub Form_Activate()
Dim dbRemote As DAO.Database

If Me.DayofWeek = "sat" Or Me.DayofWeek = "sun" Then
DoCmd.Quit
Else

Set dbRemote = DBEngine.OpenDatabase("\\server16\mrs\schedule1_be.mdb")
dbRemote.Synchronize "\\pghpart_files\\publik\mrs\schedule1CCB_be.mdb"
Set dbRemote = Nothing
DoCmd.Quit
End If
End Sub