[Dx4win] DX4WIN, LoTW, and the DXCC Award

[Duane Calvin]

That is the reason I always used "ac5aa20160229.adi" (for example) as the upload file and "lotwreport20160229.adi" as the confirmation report file downloaded from LoTW.  Completely different names that are more difficult to confuse.  Not that I haven't done that, maybe once!

Duane Calvin
Sent from my iPhone

> On Feb 28, 2016, at 10:46 PM, Alan Zack <k7acz at cox.net> wrote:
> 
> One thing to be VERY VERY careful about is when you import the file from
> LOTW to DX4WIN be SURE you are using the LOTWREPORT file and not reusing the
> file you sent to LOTW.
> For example I follow Jim AD1C's style of naming my files. If I was to send
> my latest QSO's marked LoTW=Y to ARRL today I would name my file
> LOTW02282016.adi. After LoTW accepts my file I can download from LoTW my
> report. I name this file LOTWREPORT02282016.adi. I want to be VERY sure I
> import to DX4WIN from LOTW the file LOTWREPORT and not the original LOTW
> file. If you import the LOTW file you sent to LOTW all your LOTW contacts
> would incorrectly show C (cfm). You have to be careful to keep the two
> separate. Sounds simple but if you get distracted or are not paying
> attention it could happen.
> 
> Another reason to ALWAYS back up your call.DXL file before starting a LOTW
> export/import or any other changes to the log. If you screw up you can go
> back to before the mistake.
> 
> Alan K7ACZ
> 
> 
> 
> -----Original Message-----
> From: DX4WIN [mailto:dx4win-bounces at mailman.qth.net] On Behalf Of Mike Cizek
> W0VTT
> Sent: Tuesday, February 2, 2016 9:51 PM
> To: 'Ed Douglass'; 'DX4WIN Reflector'
> Subject: Re: [Dx4win] DX4WIN, LoTW, and the DXCC Award
> 
> Hello Ed,
> 
> The answers to all of your questions can be found here:
> http://dx4win.ad1c.us/
> 
> DX4WIN does not communicate directly with LoTW.  You use Trusted QSL to send
> your information to LoTW and AD1C's Compare DXCC to LoTW utility to take
> your LoTW account and compare it to your DX4WIN log.  There are several of
> us on here who are happy to help you, but please read all of Jim's
> instructions first, and that will likely answer many, if not all, of your
> questions.  GL.
> 
>