[Dxbase] Support for QSL state "Verified" -- REPORT to make adi

Tue Dec 11 06:20:03 EST 2012

I have never been able to get Clublog to recognize <LOTW_QSL_RCVD> from 
my DXB ADIF output. To get the confirmed green boxes for LOTW qsl's in 
my DXCC chart on Clublog, I had to actually perform a "download report" 
from LOTW and change the date back to the beginning to populate those in 
Clublog.
Now when I do an LOTW upload I send the adif output to both and then do 
a "download report"to DXB and then send it to merge in Clublog.
I manually export all time new confirmations and upload them but run 
of the mill confirmations get uploaded about once a year in a clear the 
exsisting log upload.
Maybe this is more work then I need to do but it has been working. I 
just need to make sure to set aside the time to do all the uploading and 
downloading at one time so no steps get overlooked.
Phil
N9LAH
On 12/11/2012 12:44 AM, Gary AL9A wrote:
> But the adif file does distinguish between the two! If you look an 
> adif output from DXB you will note two different fields - <QSL_RCVD> 
> and <LOTW_QSL_RCVD>. Each of these fields can have one of three 
> different settings - N, Y or V per the most current adif specs. 
> Problem is DXB only uses the N or Y, never the V.
>> That is what Joe is trying to overcome with his adiexportClubLog 
> report which now sets V for those records that have a card verified 
> for DXCC in the Award column of the mdb file. Joe has also queried 
> the Club Log author about the <LOTW_QSL_RCVD> setting to make sure 
> they recognize that one too. I'm sure they do otherwise the only thing 
> you could have verified are those QSLs via card. If so I expect Joe 
> will shortly make another modification to his adiexportClubLog report 
> to set the V flag for both adif fields.
>> 73,
> Gary AL9A
>>>