[Dx4win] Strange errors in ADIF export

[Dave Sharred]

HI

Just trying to cleanse a Club Log import; but it looks like I have some
corruptions in the ADIF export from DX4WIN; as shown below.

Not sure if this is a program issue, or just a database issue. I have
cleansed my log where I can

All comments appreciated!

73

Dave
G3NKC





RM3O (from 1980) - DX4WIN showed this as EU Russia but the export was
interpretted as KYRGYZSTAN. I did notice that the zone was set incorrectly
as z17 in my log entry, so maybe this screwed up things? I will try this
again

TK0KP/SAN - is showing in DX4WIN as Corsica (=OK);  but in Clublog is
showing as Sweden ! The reason appears to be that the ADIF export assigns
284 to this QSO !

<Callsign: 1A0KM/IBYO	Date: 1991-12-08 09:09:00	Band: 10	QSL: No
1A0KM/IBYO is an invalid QSO under the ARRL DXCC rules. This may depend upon
the date of your QSO. Club Log is storing this QSO, but marking it as
invalid. Set your logged DXCC ID to '0' or QSL state to 'I' to suppress
future notifications.>

I set this in the QSO window to "I" for all DXCC awards. It would appear
that this does not suppress the QSO, or set the DXCC ID to zero in the ADIF
export ?


<Callsign: FR/DJ6SI	Date: 1992-05-14 19:57:00	Band: 20	QSL: Yes
FR/DJ6SI is an invalid QSO under the ARRL DXCC rules. This may depend upon
the date of your QSO. Club Log is storing this QSO, but marking it as
invalid. Set your logged DXCC ID to '0' or QSL state to 'I' to suppress
future notifications.>

I set this in the QSO window to "I" for all DXCC awards. It would appear
that this does not suppress the QSO, or set the DXCC ID to zero in the ADIF
export ?

<Callsign: EX2A	Date: 1993-09-21 19:09:00	Band: 30	QSL: No
Your log claims BELARUS. Overriding your choice and using KYRGYZSTAN.>

DX4WIN showed KYRGYZSTAN; but it looked like the zone was shown incorrect in
the log as Z16.  The ADIF export then showed this correctly as ADIF country
135