Database synchronisation - Location correction

Synchronising locations is performed by first matching the location names, county, state and country of locations from the database being synchronised (child database) with the master database.  Where a match is found those locations become automatically paired so that  in future all changes to the location made in any of the databases will be reflected in the other databases.  During the matching process certain problems may be encountered if the details do not match.

Reasons for matching problems can include:

• The location is on the child database but is not on the master database.  In this case you can ask to synchronisation to add it to the master database and pair the two.
• The location name is spelled differently on the child and master databases.  In this case you can ask the synchronisation to pair the misspelled location with the master.  The spelling will be corrected in the child database and the two will be paired.
• The location is not in the same county/state/country as it is on the master database.  In this case you can ask the synchronisation to pair the misplaced location with the master.  The location will be put in the correct county/state/country in the child database and the two will be paired.

Once the matching has been completed, any locations which are in the master database but not in the child database will be added to the child database and paired.

Problem resolution- Location spelled differently in child database

In this case the Location Tarapaca (Chile) is spelled differently in the child database.   The list of locations in the master database is displayed.  And the problem can be resolved by finding the correct location in the master and then pairing the two.

First search for the location in the master. The name in the master is slightly different, select the master site from the search by double-clicking or pressing the Enter key so that it is the selected location in the master list.

 Then click the Pair with selected master button to pair the location.

A confirmation message will be displayed.

A location can only be paired with a single location in the master database.  If the master database location you chose has already been paired with a different location in your child database you will get an error message.

In this case you can decide to resolve the issue manually by clicking the Leave unpaired button, or, if the location in the child database is no longer required and is not used in any trips you can delete it by clicking the Delete from child button.

Problem Resolution - Duplicate or redundant location in the child database

In some cases you may have the correct location in the child in addition you may also have a misspelled or redundant location which you no longer need.

In this case you can attempt to remove the location by clicking the Delete from child button.  If the selected location has no attached sites and is not used in any trips it will be removed from the database.  If it does have attached sites or is used in any trips you will get a warning message.

In this circumstance you must click the Leave unmatched button.  When the synchronisation has completed you can open the child database and resolve the issue manually. 

Problem Resolution - Valid location in child database not in master

In some cases you may have a location in the child which is not in the master, but you want to keep that location.  Click the Add to master button, the location will be added to the master database and paired with the location in the child database.