|
|
|
|
|
|
|
|
HRecreateSubscriberReplica (Function) In french: HRecréeRéplicaAbonné
  Not available with these kinds of connection
Recreates a subscriber replica description file ( universal replication only) based on the information of the master replica (.rpm and .syn files). The master replica must be accessible (via network or UNC). The replicated files and the range of automatic identifiers used by the initial subscriber are also used by the created subscriber.
HRecreateSubscriberReplica("", "", "Subscriber1")
Syntax
<Result> = HRecreateSubscriberReplica(<Master replica directory> , <Subscriber replica directory> , <Identifier> [, <Automatic modification>])
<Result>: Integer Identifier of the subscriber replica that was created, 0 if no subscriber replica was created. <Master replica directory>: Character string Directory where the Master Replica description file (".rpm") was created (HCreateMasterReplica). This directory can be a network directory or a UNC path.
If this parameter corresponds to an empty string (""), the description file will be searched for in the current HFSQL file directory (defined in the data model editor or programmatically).
Caution: this directory must be accessible when HRecreateSubscriberReplica is executed. <Subscriber replica directory>: Character string Directory where the subscriber replica description file must be created. This file is named Replica_<Identifier>.rpl.
If this parameter corresponds to an empty string (""), the description file will be created in the current HFSQL data file directory (defined in the data model editor or programmatically). <Identifier>: Integer or character string Subscriber replica identifier. This identifier will be used by HCreateMovableReplica.
A WLanguage error occurs if the specified identifier already exists. This parameter must not correspond to an empty string (""). <Automatic modification>: Boolean - True to take into account the automatic data modification. In this case:
- Changes in the structure of the master database will be carried over to the subscriber database.
- The new items will be taken into account by the replication.
- False (default value). The automatic data modification performed on the master database is not carried over to the subscriber database.
Caution:- For existing replications, it is necessary to recreate a replication (as well as the subscribers) to implement this mechanism.
- This mechanism does not work if a unique key is added or deleted.
- This parameter is only available for replication between HFSQL databases (Classic or Client/Server).
Business / UI classification: Business Logic
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|