With a QSO selected on the Main window's Log QSOs tab, clicking the CBA button queries the selected Callbook for information about the QSO's callsign, such as name, QTH, address, CQ zone, ITU zone, and grid square - but only information missing from the QSO is populated. After the Callbook is queried,
if DXView is running, it will be directed to query the DXCC database for additional information unambiguously determinable from the current QSO's callsign and DXCC entity
if DXView is not running, the DXCC database will be queried for additional information unambiguously determinable from the current QSO's callsign and DXCC entity
If the RDA database is installed, it will be queried to provide the Districts of Russian callsigns on the date of the QSO
This CBA function operation should only be applied to recent QSOs, as information extracted from a Callbook or the DXCC database may not be correct for older QSOs.
If the Require Edit to modify logged QSOs setting is enabled and you have not clicked the Edit button before invoking the CBA function, you will be prompted to confirm your action.
The behavior of the CBA function can be modified in two ways:
Depressing the Ctrl key while clicking the CBA button means that information obtained from the Callbook, DXCC database, and RDA database will replace information present in the current QSO; for example, if the QSO's Name item currently contains Dave and the Callbook returns a Name of David, the QSO's Name item will updated to David. However, award-specific information will not be updated if the QSO is considered confirmed for that award:
DXCC prefix - will not be changed if the QSO is confirmed via QSL card or LoTW, or if DXCC award credit has been granted
CQ Zone - will not be changed if the QSO is confirmed via QSL card or authenticity-guaranteed eQSL.cc or LoTW, or if WAZ award credit has been granted
Gridsquare - will not be changed if the QSO is confirmed via QSL card or LoTW, or if VUCC award credit has been granted
IOTA - will not be changed if the QSO is confirmed via QSL card, or if IOTA award credit has been granted
Canadian Province - will not be changed if the QSO is confirmed via QSL card
Russian Oblast - will not be changed if the QSO is confirmed via QSL card
Russian District - will not be changed if the QSO is confirmed via QSL card
US State - will not be changed if the QSO is confirmed via QSL card or LoTW, or if WAS award credit has been granted
US County - will not be changed if the QSO is confirmed via QSL card or authenticity-guaranteed eQSL.cc
Depressing the Alt key while clicking the CBA button applies the above-descsribed operation to every QSO in the Log Page Display.
DXKeeper will offer to create a backup copy of your log before proceeding with the update; accepting this offer is highly recommended.
Applying the CBA operation to a large number 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.
If the QRZ.com via Pathfinder option is selected, the rate is limited by QRZ policy to one lookup per every 4 seconds; if the operation will take longer than 1 minute to complete, DXKeeper will inform you of the expected duration, and ask whether it should proceed.
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.
There are three scenarios in which the Callbook and DXCC lookup operation can alter an unconfirmed QSO's DXCC entity:
The unconfirmed 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.
The unconfirmed 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 Ctrl key was depressed when the CBA button was clicked and the RDA database indicates that on the date of an unconfirmed QSO with a Russian callsign, that callsign was active from a different Russian DXCC entity than what is logged in the QSO, the logged DXCC entity will be corrected
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 enabled, the CBA function generates a Callbook Lookup Actions Report listing each change made to each QSO, and places the report in DXKeeper's Reports folder.