Updating QSOs in the Log Page Display with Callbook and DXCC Database Information

DXKeeper Online Help Contents

 

On the Main window's Log QSOs tab, clicking the CBA button queries the selected Callbook for information such as name, QTH, address, and zone -- but this information only inserted into empty items in the current QSO. After the Callbook is queried,

This Callbook and DXCC lookup operation should only be applied to recent QSOs. Information extracted from a Callbook or the DXCC database may not be correct for older QSOs.

This operation can be modified in two ways:

Depressing  both the Alt and Ctrl keys while clicking the CBA button combines both modifications: information in all QSOs in the Log Page Display will be replaced by information obtained from the database queries.

If you click the CBA button with the Alt key depressed, DXKeeper will offer to create a backup copy of your log before proceeding with the update; accepting this offer is highly recommended. Applying these operations to large numbers of QSOs can take significant time, particularly if you haven't copied your Callbook's database from CDROM to a hard drive, and even more so if you're using an internet-accessible service as a callbook.

There are two scenarios in which the Callbook and DXCC lookup operation can alter a a QSO's DXCC entity:

  1. The QSO's DXCC entity is Alaska, Hawaii, or the US, but the state returned by the Callbook does not match the entity; if the Ctrl key depressed when the CBA button was clicked, DXKeeper will correct the QSO's DXCC entity to match the state returned by the Callbook.

  2. The QSO's DXCC entity is unspecified and the callsign is not an aeronautical or maritime mobile stations, and is not preceded by an exclamation point; if the DXCC database can unambiguously determine the entity from the callsign, DXKeeper will update the QSO with this DXCC entity.

If the Alt key is depressed when the  CBA button is clicked, all instances of the above two scenarios will be displayed in a report when the operation completes. 

If a QSO specifies a DXCC entity that formally defines a set of Primary Administrative Subdivisions, the Callbook returns a Primary Administrative Subdivision code or abbreviation, and if the Subdivisions box is checked on the Config window's Awards tab, then DXKeeper will determine whether that code or abbreviation is valid. If the QSO's DXCC entity also formally defines a set of Secondary Administrative Subdivisions, the Callbook returns a Secondary Administrative Subdivision code or abbreviation, and if the Subdivisions box is checked on the Config window's Awards tab, then DXKeeper will also determine whether that code or abbreviation is valid. If either subdivision is found to be invalid and the Alt key was not depressed, then DXKeeper will display a message and leave the QSO's subdivision unmodified. If either subdivision is found to be invalid and the Alt key was depressed, then the QSO's subdivision will be updated with the invalid code or abbreviation, the QSO's PrimaryInvalid or SecondaryInvalid item will be set to Y, and when the Alt-CBA operation has updated all QSOs a message will be displayed indicating that one or more QSOs were imported with invalid subdivisions. The Broke filter can be used to filter the Log Page Display to show QSOs whose PrimaryInvalid or SecondaryInvalid items are set to Y.

If the Require Edit to modify logged QSOs setting is enabled and you have not clicked the Edit button before initiating a callbook lookup, you will be prompted to confirm the lookup action.