Associating a callsign with a specific dxcc entity

RUMlog, the Next Generation. Completely rewritten.
VE3MM
Posts: 5
Joined: Thu 26. Oct 2017, 01:17

Associating a callsign with a specific dxcc entity

Unread post by VE3MM » Sat 18. Aug 2018, 11:06

I worked TX5T (FO/A) and the contact logs as DXCC ?. I tried adding TX5T to the preferences DXCC exception list but it does not associate the change the QSO information to FO/A. Can you please let me know the proper procedure for this.

User avatar
DL2RUM
Administrator
Posts: 1916
Joined: Mon 27. Aug 2007, 13:36
Location: JO40DF

Re: Associating a callsign with a specific dxcc entity

Unread post by DL2RUM » Sat 18. Aug 2018, 13:47

73 and best dx de Tom, DL2RUM

VE3MM
Posts: 5
Joined: Thu 26. Oct 2017, 01:17

Re: Associating a callsign with a specific dxcc entity

Unread post by VE3MM » Sun 19. Aug 2018, 00:50

Thanks Tom. I checked to make sure the latest club log file is installed and TX5T is correctly associated with FO(A).
If I log a new contact with TX5T it shows up with the correct DXCC entity.
However I have two other contacts with TX5T and they still show ?? in the DX entity column.
Is there a way to get the entities recognized? I tried restarting RumlogNG but this didn't do it.

73
Rick ve3mm

User avatar
DL2RUM
Administrator
Posts: 1916
Joined: Mon 27. Aug 2007, 13:36
Location: JO40DF

Re: Associating a callsign with a specific dxcc entity

Unread post by DL2RUM » Sun 19. Aug 2018, 04:26

All QSO and DXCC entity information are stored within the database record. There is no automatic update.
From the document linked above:
When you have logged a QSO already before you made changes, you have to recalculate the DXCC entity for all affected QSOs. To do this, select the affected QSOs and use Menu–>Logbook–>Recalculate DXCCs.
73 and best dx de Tom, DL2RUM

VE3MM
Posts: 5
Joined: Thu 26. Oct 2017, 01:17

Re: Associating a callsign with a specific dxcc entity

Unread post by VE3MM » Sun 19. Aug 2018, 12:01

Hi Tom
This worked fine. Thanks for your help. Have a good day.
73
Rick ve3mm

Post Reply