[AccessD] Replication Manager

I bow to your research.  I am working primarily in .Net now, so I don't
even HAVE Access 2003.

Charlotte Foust


-----Original Message-----
From: MartyConnelly [mailto:martyconnelly at shaw.ca] 
Sent: Thursday, June 09, 2005 11:57 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Replication Manager


According to Michael Kaplan's posts dating to last june, it is not 
included as of that date
However you can install the synchronizer with the special extra Jet SP 
8.0 replication upgrade
and then use JRO code, Getz has a couple of hundred pages on vba jro 
coding in one of his ADH
books 2000 or 2002 vol 2.
I don't have the latest VSTO to check for sure.

Charlotte Foust wrote:

>It may be in VSTO, along with the rest of the developer tools for 
>Access.
>
>Charlotte Foust
>
>
>-----Original Message-----
>From: MartyConnelly [mailto:martyconnelly at shaw.ca]
>Sent: Tuesday, June 07, 2005 9:25 AM
>To: Access Developers discussion and problem solving
>Subject: Re: [AccessD] Replication Manager
>
>
>RepMan 4.0  is on the Office XP Developers Edition, not the Pro 
>Edition, funnily enough there is no RepMan for 2003. I don't know what 
>you do here use VB.Net and JRO or old version of RepMan with Access 
>2003
>
>Documentation within MS-Access 2003 states that this tool is still
>required to setup Internet replicated Access databases.
>http://support.microsoft.com/default.aspx?scid=kb;en-us;828089
>
> so, unless you have that RepMan from XP
>.... you need to write your own using JRO or use a tool like TSI
>Synchronizer http://www.trigeminal.com/repl-ication/synch.asp?1033
>
>Note that this is not really true, either -- the TSI Synchronizer 
>depends upon you having the Jet Synchronizer (which comes with 
>Replication Manager).
>
>You do not need Replication Manager to use all forms of Jet 
>replication.
>
>Replication
>Manager is a tool for implementing certain advanced replication 
>functionalities such as synchronizer configuration for indirect or 
>internet replication or for changing the the retention period of a 
>replication set. Also, you do not need to have a copy of Replication 
>Manager on every computer (and probably shouldn't) since it is only an 
>administrators tool. Anything that can be done with Replication manager

>can also be accomplished using DAO or JRO code
>
>Jet 8 SP has a seperate update for replication
>
>http://support.microsoft.com/default.aspx?kbid=321076
>
>This shows installation procedures for RepMan
>
>Internet Synchronization with the Microsoft Jet Database Engine: A
>Technical Overview
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnacc2
k
>/html/intrjet4.asp
>
>Make sure you have read the replication faq and understand indirect and
>direct synchronization
>
>http://support.microsoft.com/kb/q282977/
>
>Here's some DAO code to illustrate a basic synchronization process of 
>BE
>
>over a Lan...
>'Courtesy Lambert Heenan
>Private Sub btnUpdateMaster_Click()
>Dim msg As String
>Dim sReplicaDb As Variant
>Dim sMainStore As String
>Dim db As Database
>
>    On Error GoTo btnUpdateMaster_err
>    'First get the path to the replica file we will synch. with.
>    msg = "This procedure will update the MASTER database with one or 
>more replica databases.@"
>    msg = msg & "Do you with to continue?@"
>    If MsgBox(msg, vbYesNo Or vbQuestion, "Synchronize Master 
>Database") = vbYes Then
>
>        sReplicaDb = sDataToSynchFrom() '
>
>' sDataToSynchFrom() is a function that returns the full path to an MDB

>file
>
>        If sReplicaDb & "" = ""  Then Exit Sub
>        sMainStore = GetAttachedDbName(GetFirstAttachedtable)
>
>' GetAttachedDbName() is a function that returns the full path to the 
>back end database ' given the name of one of the linked tables
>
>        ' sanity check
>        If sMainStore = sReplicaDb Then
>            MsgBox "Cannot synchronize your main data file with 
>itself. at Please select the correct replica data file to synchronize 
>with.@", , "Invalid data file selected"
>            Exit Sub
>        End If
>        DoCmd.Hourglass True
>' here is where the synchronization takes place
>        Set db = OpenDatabase(sMainStore)
>' this does a one-way synchronizatin - just importing changes in the 
>data. ' you can also do two way using the constant "dbRepImpExpChanges"
>        db.Synchronize sReplicaDb, dbRepImportChanges
>        RenameSynchedFile CStr(sReplicaDb)
>        DoCmd.Hourglass False
>        MsgBox "Synchronization completed", , "Synchronize Master 
>Database"
>    End If
>btnUpdateMaster_Click_Exit:
>    Set db = Nothing
>    Exit Sub
>btnUpdateMaster_err:
>    DoCmd.Hourglass False
>' put your favorite error handler here
>    MsgBox "Error synchronizing with " & sReplicaDb & "@" & 
>Err.Description & "@Error number " & Err.Number
>    Resume btnUpdateMaster_Click_Exit
>End Sub
>
>
>Barbara Ryan wrote:
>
>  
>
>>Where I can I find Replication Manager for Access 2002?  Is it a
>>separate interface from the Replication option under Tools in Access 
>>2002?  I can't seem to locate it on the Office XP Pro installation CD.
>>
>>Thanks,
>>Barb Ryan
>> 
>>
>>    
>>
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada



-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com