I am seeing the same thing. I will take a look at it.
However, this ADIF record is WRONG. The DXCC should be the ARRL numeric code. There is no official list of DXCC prefixes. I take out the DXCC from the ADIF file, and it correctly imports as 9A, using the call for the lookup.
Where did this .adi come from?
I will fix LOGic to ignore invalid DXCC entries in the ADIF file. Meanwhile, turn off import of DXCC in tools/setup/log fields. I am curious as to how it is coming up with KH8 hihi. The ARRL designator for KH8 is 9 so I suppose that is the closest match it can find on that field.
I am not seeing any problems in the prefix table with 9A or KH8. It does the proper lookup from the log form.
Quote: Sometimes LOGic sets the wrong DXCC due to the prefix table not being accurate.
I just want to point out that as far as I know, Logic's prefix table is accurate. The fact of the matter is that you cannot always determine the DXCC from a callsign.
Tnx & 73,
Dennis WN4AZY