|
|
|
|
|
|
|
|
|
|
- List of data files to be replicated
HRplAddFile (Function) In french: HRplAjouteFichier Adds a data file to a universal replication. Note: The corresponding physical data file must be present on the subscriber computer. HRplAddFile("P:\MSG\MSG.RPM", "Paris", "NewFileToReplicate")
Syntax
<Result> = HRplAddFile(<Master replica directory> , <Identifier> , <List of tables to replicate>)
<Result>: Boolean - True if the data file(s) have been added to the replication,
- False otherwise.
<Master replica directory>: Character string Directory where the master replica description file ("rpm" file) 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 directory of HFSQL data files (defined in the data model editor or through programming).
Note: This directory must be accessible when HRplAddFile is executed. <Identifier>: Integer or character string Subscriber replica identifier. This identifier is returned by HCreateSubscriberReplica. This identifier will be used by HCreateMovableReplica. <List of tables to replicate>: Character string This list has the following format:
<Data file name> [+ TAB + <Date item name>]
[+ <CR> + <Name of data file 2> [+ TAB + <Name of date item 2>]]... Caution: - The order of data files is important. This order is determined by the dependencies between the data files (see Remarks).
- The name of the Date item is required for databases other than HFSQL. This item must correspond to an item of the data file updated when the corresponding record is added or modified. This operation must be performed by the application.
Remarks List of data files to be replicated The list of data files to be replicated must be specified using the following syntax: <Data file name> [+ TAB + <Date item name>]
[+ <CR> + <Name of data file 2> [+ TAB + <Name of date item 2>]]... The order of data files is important. This order is determined by the dependencies between the data files. Let's take the following example: - Records in data file 1 are linked to records in data file 2.
- The record must be present in data file 2 so that it can be added in data file 1 in compliance with integrity rules.
In this case, data file 1 must be first in the list. Let's look at an example with three data files ("Customer", "Order" and "Order line", linked by cardinalities (0,n) - (1,1)). In this case, the order should be: - the "Customer" data file first (to add an order, you need a customer),
- then the "Order" data file (to add an order line, you need a order),
- and finally the "Order line" data file.
Business / UI classification: Business Logic
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|