Guys,
I just checked my Club Log and all my confirmations from Wake, KH9,
are there and my totals have not changed.
Looking on Mr. Google for the "fix" I found the following two
suggestions:
Sep 24, 2022
— If your totals are way out of date,
you may want to consider re-uploading your whole log
to Club Log to get them right.
And this one:
https://clublog.freshdesk.com/support/solutions/articles/53208-why-doesn-t-the-number-of-dxccs-in-club-log-match-my-logger-
So you may just want to upload your full log, then look at the email
Club Log sends you. It will tell you things it finds wrong with
your log.
Here is a sample of the email I received after my last full upload
to Club Log:
Dear W8TN,
While processing your ADIF file for Club Log, the following possible problems were detected. Your log may be correct, but if necessary you can resolve these problems and create a new ADIF. If you make changes, it's recommended that on your next upload you use the option to clear your existing log, to avoid leaving prior records in Club Log.
If you would like to discuss these problems, you can ask the volunteer team on the helpdesk for assistance. You can disable these emails from the Settings page if you prefer.
Join us on Discord: https://discord.gg/NSX4E9xYW2
Information on DXCC mappings: https://clublog.freshdesk.com/solution/categories/59801
Ask for help from the volunteer team: https://clublog.freshdesk.com/
73 de Michael G7VJR
* Software: LOGGER32
* File name: 2025-12-22_Full_Log.ADI (5.57 MB)
* New/updated QSOs: 13,872
Callsign: VR1PJ Date: 1980-09-20 04:55:01 Band: 20 QSL: Yes
'VR1PJ' does not map by prefix or exception to any DXCC on the date in question. Skipping QSO.
See https://clublog.org/test.php?c=VR1PJ&t=338273701 for details.
Note: There are comments about VR1PJ in the Club Log database, which may provide further details. See https://clublog.org/test.php?c=VR1PJ&t=338273701.
Callsign: 3C0AC Date: 1982-01-27 15:40:00 Band: 15 QSL: Yes
'3C0AC' is not known to have been active from ANNOBON on this date. As a precaution, this QSO will be stored but marked as invalid for DXCC. If this callsign is valid, it can be whitelisted - you are invited to send feedback. For a detailed explanation, please see: http://clublog.freshdesk.com/solution/articles/77534-whitelists
Callsign: AAZ Date: 2001-05-12 21:26:00 Band: 20 QSL: No
Invalid callsign - skipping QSO.
'AAZ' does not map by prefix or exception to any DXCC on the date in question. Skipping QSO.
Callsign: RX9AT Date: 2017-12-26 19:54:00 Band: 2 QSL: Yes
Your log claims EUROPEAN RUSSIA. Overriding your choice and using ASIATIC RUSSIA.
Note: RX9AT may be located in Europe, but this prefix counts for Asiatic Russia for DXCC purposes.
I did check on RX9AT and, in fact, his QSL said Asiatic Russia but
for some reason, at the time of the QSO, there were discussions on
the EME Chat Page about him actually being in European Russia. I
have now changed my Logger32 entry to Asiatic Russia.
The AAZ contact was from Armed Forces Day and of course does not
count for DXCC.
The VR1PJ QSO was in 1980 and the 3CØAC QSO was in1982 so I have not
dug back through my QSL's to see what the situation was with those
two contacts.
73, Clark, W8TN