PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • Principle of the assisted universal replication
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Overview
To simplify the implementation of the universal replication between the data of a remote application and a central database, WINDEV, WEBDEV and WINDEV Mobile propose:
  • the creation of a replication via a replication editor (ReplicEdit). This editor is used to define the characteristics of a replication.
  • the implementation of an automatic replication on the data of an application. The replication is directly performed by the end users via two tools:
  • the implementation of a programmed replication included in an application via the WLanguage functions. These functions are used to handle a replication and to perform the synchronization.
    See Implementing a programmed assisted universal replication for more details.
Notes:
  • No replication can be directly deployed on a computer without using an application.
  • Some features are not available in this version. See the Limitations regarding the assisted universal replication for more details.
  • From version 17:
    • The replication files created with an application or a site in version 17 (or later) cannot be handled by an application or a site in version 16 (or earlier).
    • The applications or sites in version 17 (or later) can handle the replication files created with an application or site in version 16 (or earlier).
  • Versions 19 and later
    The assisted universal replication is available for the replication of mobile data (Android or iOS). See Replication of mobile data (Android or iOS) for more details.
    New in version 19
    The assisted universal replication is available for the replication of mobile data (Android or iOS). See Replication of mobile data (Android or iOS) for more details.
    The assisted universal replication is available for the replication of mobile data (Android or iOS). See Replication of mobile data (Android or iOS) for more details.
Note: From version 19, HFSQL is the new name of HyperFileSQL.
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: The replication is directly performed between the local database and the master database. This replication mode is recommended when a computer must connect to the local network for example. This replication mode requires no specific configuration.
  • replication by server: the replication is performed via a replication server. The transfer of replicas is automatically managed.
The replication via server can be performed with immediate replica: in this case, the data is immediately synchronized. 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 example (a salesperson synchronizes every evening with the office).
The replication by server can be performed with delayed replica: in this case, the data is synchronized when the exchanges are performed 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 (whenever an order is placed for example).
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 required version
  • Version 12
This page is also available for…
Comments
Click [Add] to post a comment