[Dx4win] LOTWREPORT - NOT FOUND

[John Shaw]

 Hi Randy yes it's a mine field, which is the most correct information,
sometimes they realise their mistake and upload again.  I have also found
people sometimes do the QTH change when they operated from a different
location then upload their whole log and screw up everything previously
loaded.  To save my sanity I accept that there will be errors at this level
and move on. :-)

I think the Cnfm flag gets set differences or not.

73 John ZL1BYZ.

-----Original Message-----
From: dx4win-bounces at mailman.qth.net [mailto:dx4win-bounces at mailman.qth.net]
On Behalf Of Randy Farmer
Sent: Thursday, 15 December 2011 15:36
To: dx4win at mailman.qth.net
Subject: Re: [Dx4win] LOTWREPORT - NOT FOUND

I see this all the time and it's mostly because of a mismatch in something
like a county between what's in your log and what's in the LoTW confirmation
record. I get a lot of these after I do a state QSO party and work some
mobile/portable stations not in their home county. 
When they upload to LoTW they just use their regular certificate that
populates their home county. DX4WIN sees this as a mismatch and doesn't set
the LoTW confirm flag for the QSO. It's up to you to correct the log or just
manually set the LoTW Cnfm flag.