ICheckIn.CheckInFromDeltaFile Method

Checks in changes from a delta database.

[Visual Basic .NET]
Public Function CheckInFromDeltaFile ( _
    ByVal parentDB As IWorkspaceName, _
    ByVal checkoutName As String, _
    ByVal fileName As String, _
    ByVal dcOption As esriExportDataChangesOption, _
    ByVal reconcileCheckout As Boolean, _
    ByVal createOIDMappingTable As Boolean _
) As Boolean

[C#]
public bool CheckInFromDeltaFile (
    IWorkspaceName parentDB,
    string checkoutName,
    string fileName,
    esriExportDataChangesOption dcOption,
    bool reconcileCheckout,
    bool createOIDMappingTable
);

[C++]
HRESULT CheckInFromDeltaFile(
  IWorkspaceName* parentDB,
  BSTR checkoutName,
  BSTR fileName,
  esriExportDataChangesOption dcOption,
  VARIANT_BOOL reconcileCheckout,
  VARIANT_BOOL createOIDMappingTable
);

[C++]
Parameters
parentDB [in]

  parentDB is a parameter of type IWorkspaceName*
checkoutName [in]

  checkoutName is a parameter of type BSTR
fileName [in]

  fileName is a parameter of type BSTR
dcOption [in]

  dcOption is a parameter of type esriExportDataChangesOption
reconcileCheckout [in]

  reconcileCheckout is a parameter of type bool
createOIDMappingTable [in]

  createOIDMappingTable is a parameter of type bool

Product Availability

Remarks

The CheckinfromDeltaFile method applies the changes from a delta database (dcOption = esriExporttoAccess) or a delta XML file (dcOption = esriExporttoXML). See the DataChangesExporter for more information on delta files.

The checkoutName is needed to identify the check-out that is being checked in.

If createOIDMappingTable is True, tables are created in the parent replica geodatabase that describe the changes that are checked in. These tables are named <check-out name>_OM and <check-out name>_RC. If tables with these names already exist, they are over-written.

The <check-out name>_OM table records the pre- and post- check-in ObjectID values for new features/rows that have been added. The <check-out name>_RC table records all the changes made to the checked out data which include inserts (0), updates (1) and deletes (2).

Conflicts

If reconcileCheckout is TRUE, the changes are applied to the check-out version and this version is reconciled with its parent version. If reconcileCheckout is FALSE, the changes are applied to the check-out version, but no reconcile is performed.

If reconcileCheckout is TRUE and there are no conflicts during reconcile, a FALSE is returned, otherwise TRUE is returned. Conflicts can occur if a feature is edited in the check-out database and in the parent version of the parent database. 

You should never edit the check-out version prior to check in. During check in, any coincidental changes are over-written with changes from the check-out database without notification of a conflict.

If you set reconcileCheckout to TRUE and there are conflicts or if reconcileCheckout is set to FALSE, the check-out version is updated and remains on the parent geodatabase. This allows you to manually reconcile at a later time. If you set reconcileCheckout to TRUE and there are no conflicts, the check-out version is removed.

See Also