ACC: How to Use the ReplicationConflictFunction Property

MORE INFORMATION

Creating a Custom Conflict Resolver

• Synchronization conflicts
• Synchronization errors
• Design errors

Synchronization Conflicts

   Sub ViewSyncConflict()
      Dim Db As DATABASE
      Dim Td As TableDef
      Dim i as Integer
      Set Db = CurrentDb
      ' Step backward through the TableDefs collection so you
      ' do not miss any tables when you delete conflict tables.
      For i = Db.TableDefs.Count - 1 to 0 Step -1
         Set Td = Db.Tabledefs(i)
         If (Td.ConflictTable <> "") Then
            ' Open a recordset based on the conflict table.
            ' Insert code to do conflict resolution.
            ' Delete the conflicting record when you are done.
            ' Delete the conflict table when all its records are deleted.
            ' Set the ConflictTable property to "".
         End If
      Next i
   End Sub

Synchronization Errors

• A table-level validation rule is applied and other replicas have data that does not satisfy the rule.
• A duplicate key error occurs because two different replicas entered the same primary key into a table.
• A referential integrity error occurs because a primary table record is deleted in one replica, and a record is added to a related table in another replica.
• A record is locked when synchronization occurs.

  Sub ViewSyncError()
      Dim Db As DATABASE
      Dim Rs As Recordset
      Dim MsgString As String
      On Error GoTo ErrorHandler
      Set Db = CurrentDb
      Set Rs = Db.OpenRecordset("MSysErrors", dbOpenSnapshot)
      Rs.MoveLast
      If Rs.RecordCount > 0 Then
         Rs.MoveFirst
         Do Until Rs.EOF
            ' Build the error message string.
            MsgString = "Table ID: " & Rs!TableGUID & vbCr
            MsgString = MsgString & "Record ID: " & Rs!RowGUID & vbCr
            MsgString = MsgString & "Operation: " & Rs!Operation & vbCr
            MsgString = MsgString & "Failed Because: " & Rs!ReasonText
            MsgBox MsgString
            Rs.MoveNext
         Loop
      End If

   ExitProc:
      Exit Sub

   ErrorHandler:
      ' If the MSysErrors table is empty...
      If Err.Number = 3021 Then
         Resume ExitProc
      ' display any other error that occurs.
      Else
         MsgBox Err.Description
         Resume ExitProc
      End If
   End Sub
				

Design Errors

  Sub ViewDesignError()
      Dim Db As DATABASE
      Dim Rs As Recordset
      Dim MsgString As String
      On Error GoTo ErrorHandler
      Set Db = CurrentDb
      Set Rs = Db.OpenRecordset("MSysSchemaProb", dbOpenSnapshot)
      Rs.MoveFirst
      Do Until Rs.EOF
         ' Build the error message string.
         MsgString = "Operation: " & Rs!Command & vbCr
         MsgString = MsgString & "Failed Because: " & Rs!ErrorText
         MsgBox MsgString
         Rs.MoveNext
      Loop

   ExitProc:
      Exit Sub

   ErrorHandler:
         ' If the MSysSchemaProb table does not exist.
         If Err.Number = 3078 Then
            Resume ExitProc
         ' If the MSysSchemaProb table is empty.
         ElseIf Err.Number = 3021 Then
            Resume ExitProc
         ' Display any other error that occurs.
         Else
            MsgBox Err.Description
            Resume ExitProc
         End If
   End Sub
				

Putting It All Together

   Function MyCustomFunction()
      ViewSyncConflict
      ViewSyncError
      ViewDesignError
   End Function
				

Setting the ReplicationConflictFunction Property

Setting the ReplicationConflictFunction Programmatically

1. Open the Design Master database for the replica set.
2. Create a module and type the following procedure:

         Sub SetCustomFunction(FunctionName As String)
            Dim Db As DATABASE, Ctr As Container, Doc As Document
            Dim Prp As Property
            On Error GoTo ErrorHandler
            Set Db = CurrentDb
            Set Ctr = Db.Containers!Databases
            ' Set Document variable pointing to user defined document.
            Set Doc = Ctr.Documents!UserDefined
            ' Set the ReplicationConflictFunction property if it exists.
            Doc.Properties!ReplicationConflictFunction = FunctionName
         Exit Sub
   
         ErrorHandler:
            ' If the property does not exist...
            If Err.Number = 3270 Then
               ' create ReplicationConflictFunction property and set its
               ' value.
               Set Prp = Doc.CreateProperty("ReplicationConflictFunction", _
                   dbText, FunctionName)
               ' Append the new property to the collection.
               Doc.Properties.Append Prp
               ' Resume the main procedure.
               Resume Next
            Else
               ' Display any other error that occurs.
               MsgBox Err.Number & ": " & Err.Description, vbCritical
            End If
         End Sub
   					

3. To test this function, type the following line in the Debug window, and then press ENTER:

   SetCustomFunction("MyCustomFunction()")

Setting the ReplicationConflictFunction Through the User Interface

1. Open the Design Master database for the replica set.
2. On the File menu, click Database Properties.
3. In the <DatabaseName> Properties dialog box, click the Custom tab.
4. Set the following properties:

   Name: ReplicationConflictFunction
   Type: Text
   Value: MyCustomFunction()

5. Click OK to close the Properties dialog box.