Hi Paul I agree of course with everything that you say; but the /SAN is on the QSL card....
The real problem is DX4WIN correctly identifies it as Corsica in the logging program, but it is the ADIF export file from DX4WIN that is causing the errors. If they were consistent, then I would know how to fix the file! Most of the errors I reported were in this category I think... 73 Dave G3NKC -----Original Message----- From: F6EXV [mailto:[email protected]] Sent: 28 December 2009 12:25 To: 'Dave Sharred'; 'Dx4win' Subject: RE : [Dx4win] Strange errors in ADIF export Hi all re TK0KP/SAN, obviously the SAN is not part of the officuial callsign, just an addition by the op to indicate he was operating from the Sanguinaires islands (IOTA) DX4Win will take that SAN for Sweden, which is logical with such a SA suffix... Basically, the SAN should be taken off the logged callsign. 73 Paul F6EXV -----Message d'origine----- De : [email protected] [mailto:[email protected]] De la part de Dave Sharred Envoyé : lundi 28 décembre 2009 01:05 À : Dx4win Objet : [Dx4win] Strange errors in ADIF export 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 ______________________________________________________________ Dx4win mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html ______________________________________________________________ Dx4win mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
