Ernie Walls wrote:
> I think I have read how to resolve this issue before, but cannot find
> the thread in the archives.
>
> The issue - LOTW just today advised me that it had confirmed a QSO that
> is not in my log!!!! I think!
That has happened to me too few times. The odd thing is that all of the
QSO's that were reported by Dx4win not being in my log, they were all
there. For some odd reason Dx4win didn't recognise the QSOs eventhugh
all the QSO details were exactly the same.
>
> How is that so, and is there a way to, relatively easily, I reconcile
> DX4Win with LOTW.
What I did was I downloaded all the confirmed QSL details from LOTW and
imported the data into a new clean log file. Then I made a comma
deliminated file from the LogBook window in Dx4win with the Write to
file -function. Then I opened my normal log file and made an F8 search
for Upl Cnf Y QSOs. I exported that the same way to text file. After
that I imported both of the files to Excel and compared the QSO data by
setting the both files side by side. It was quite easy to find which 5
QSOs had not been confirmed in Dx4win eventhough the QSOs were in the
downloaded file.
Juha OH6XX
From [EMAIL PROTECTED] Sun May 7 12:13:46 2006
From: [EMAIL PROTECTED] (Paul van der Eijk)
Date: Sun May 7 12:17:42 2006
Subject: [Dx4win] LOTW confirms a NIL
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Juha,
For the next version I create a report for the QSOs that were not found
but confirmed in the ADIF file. Up to now it looks like that one file contains
the QSO time including seconds, the other file does not include the seconds.
This difference makes the lookup fail.
I still do not understand where the difference comes from. When DX4WIN
writes an ADIF file, the seconds are included. When the file comes back
from LOTW, the seconds are still there. But it seems that there is a way to
drop the seconds, but I fail to understand how this happens.
Any insight is appreciated!
--Paul
At 11:50 AM 5/7/2006, Juha Rantanen wrote:
>Ernie Walls wrote:
>>I think I have read how to resolve this issue before, but cannot find
>>the thread in the archives.
>>The issue - LOTW just today advised me that it had confirmed a QSO that
>>is not in my log!!!! I think!
>
>That has happened to me too few times. The odd thing is that all of the QSO's
>that were reported by Dx4win not being in my log, they were all there. For
>some odd reason Dx4win didn't recognise the QSOs eventhugh all the QSO details
>were exactly the same.
>
>>How is that so, and is there a way to, relatively easily, I reconcile
>>DX4Win with LOTW.
>
>What I did was I downloaded all the confirmed QSL details from LOTW and
>imported the data into a new clean log file. Then I made a comma deliminated
>file from the LogBook window in Dx4win with the Write to file -function. Then
>I opened my normal log file and made an F8 search for Upl Cnf Y QSOs. I
>exported that the same way to text file. After that I imported both of the
>files to Excel and compared the QSO data by setting the both files side by
>side. It was quite easy to find which 5 QSOs had not been confirmed in Dx4win
>eventhough the QSOs were in the downloaded file.
>
>Juha OH6XX
>_______________________________________________
>Dx4win mailing list
>[email protected]
>http://mailman.qth.net/mailman/listinfo/dx4win
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Paul van der Eijk (KK4HD)
[EMAIL PROTECTED]
http://www.dx4win.com
