DXCC count in V 2.6.16 #3200
-
|
Following install of V2.6.16 I noticed one DXCC less in the count. Georgia is no longer included given the callsign K6VHF/4L. This call was previously valid in Cloudlog and it's recognised and included in LoTW. Any views on this, is it an error? Steve M0SKM |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
|
Odd, nothing has changed to my knowledge when it comes to dxcc code |
Beta Was this translation helpful? Give feedback.
-
|
This morning before update the DXCC count was 105; it's now 104 and definitely Georgia that altered. It was a straightforward update which otherwise was great. LoTW still says 105 so I'm not bothered too much. |
Beta Was this translation helpful? Give feedback.
-
|
Will dig into it a bit more this evening see what perhaps changed, guess other thing todo might be run the Update Country Files although that shouldn't really change the numbers! |
Beta Was this translation helpful? Give feedback.
-
|
I should have said; I had run Update Country Files already and it could be what provoked it. Got a hospital stay coming up and my mind is elsewhere. Hope you find something. |
Beta Was this translation helpful? Give feedback.
-
|
Thats helpful place to start debugging :) Good luck with the hospital stay! |
Beta Was this translation helpful? Give feedback.
-
|
Just located this; see image |
Beta Was this translation helpful? Give feedback.
-
|
Ok that shows the issue the wrong DXCC is selected if you go edit the QSO and set the DXCC to Georgia |
Beta Was this translation helpful? Give feedback.
This morning before update the DXCC count was 105; it's now 104 and definitely Georgia that altered. It was a straightforward update which otherwise was great. LoTW still says 105 so I'm not bothered too much.
Thanks for the quick reply Peter.