ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

This content has been translated automatically.  Click here  to view the French version.
Help / WLanguage / Managing databases / HFSQL / Managing replications / Universal replication
  • Overview
  • Principle of the assisted universal replication
WINDEV
WindowsLinuxJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac Catalyst
Others
Stored procedures
Overview
To easily establish the universal replication between the data of a remote application and a central database, WINDEV and WEBDEV allow you to:
  • create a replication via a replication editor (ReplicEdit). This editor is used to define the characteristics of a replication.
  • implement an automatic replication on the data of an application. The replication is directly performed by the end users via two tools:
    • ReplicSynchro, used to perform a replication.
    • ReplicAdmin, used to manage the replications.
    For more details, see Implementing an automatic assisted universal replication.
  • implement a programmed replication included in an application via WLanguage functions. These functions are used to handle a replication and to perform the synchronization.
    For more details, see Implementing a programmed assisted universal replication.
Remarks:
Principle of the assisted universal replication
The purpose of the assisted universal replication is to propose a quick replication for any type of application.
The assisted universal replication proposes the following modes of replication:
  • direct replication: replication is performed directly between the local base and the master base. This replication mode is recommended when a computer must connect to the local network for example. This replication mode requires no specific configuration.
  • replication per server: replication is performed via a replication server. The transfer of replicas is automatically managed.
Server replication can be performed with immediate replica: in this case, data is synchronized immediately.. The subscriber database sends the data to replicate, the replication is performed and the subscriber database retrieves the data to update. This operation can take quite a long time. This replication mode is recommended for a daily synchronization for instance (a salesperson synchronizes every evening with the office).
Server replication can be carried out with deferred replication: in this case, data is synchronized as it is exchanged with the server.. When the server receives the data to replicate, it automatically prepares the data to return. This data will be returned during the next synchronization. This replication mode is recommended for a periodic synchronization for instance (whenever an order is placed).
Related Examples:
WD Universal Replication Training (WINDEV): WD Universal Replication
[ + ] This examples explains how to use the universal replication to synchronize data of different sites.
The universal replication is used to synchronize the data of a site (master site) with the same data of one or more replicated sites (subscriber sites). The data structures are identical on each site but they can be exploited via different data managers. HFSQL Classic and Access will be used in this example.
The example presents the processes that must be included in your applications to allow the user, via a simple action (menu, button, ...), to:
- create a master replica,
- create one or more subscriber replicas,
- see and modify the data of these replicas,
- export the created or modified data to a site (portable replica),
- import the created or modified data into another site...
Minimum version required
  • Version 12
This page is also available for…
Comments
Click [Add] to post a comment

Last update: 10/04/2024

Send a report | Local help