[Dxbase] LoTW induced errors in DXbase

Sun Jun 13 17:46:20 EDT 2004

Bill
Unfortunately, people have entered qso's into LoTW with incorrect zone info, incorrect
state, iota, grid info and probably they don't even have their own names correct.
Another issue is Canadian Provinces being shown as states.
What I do to avoid this problem is to NOT choose the full details option when downloading
LoTWReport.adi for myself.
As a beta tester for LoTW, I reported this problem to the folks at LoTW and they are aware
of it.
It looks like they will have to 'reject' qso's that a person submits with a report
indicating that they have incorrect info.
This can be a problem I'm sure you can see.
Hopefully they can fix it in a future release of the software.
----- Original Message ----- 
From: "William H. Hein" <Bill at NT1Y.com>
To: "DXbase Reflector" <dxbase at mailman.qth.net>
Cc: "Patton, David NN1N" <nn1n at arrl.org>
Sent: Sunday, June 13, 2004 2:48 PM
Subject: [Dxbase] LoTW induced errors in DXbase
I submitted a DXCC application via LoTW recently and received 562 credits.
I am manually entering these credits into Dxbase 2005, ticking the DXCC box
in the Award field of each QSO record.
While doing this, I noticed that the Dxbase's LoTW import is doing strange
things to my logbook data. For example, I received 160m DXCC credit from
LoTW for an EA4KD QSO on 1996-Jan-10. Back in 1996, I had logged this QSO
with the proper CQ (14) and ITU (37) zones. The QSO record in LoTW,
however, had incorrect CQ (37) and ITU (14) zone data. (This happens a lot,
LoTW is full of bad zone data.) Dxbase seems to have entered this QSO into
my logbook a second time with the bad zone data and marked that one as LoTW
confirmed, the zone data for the original QSO remained as is (that is,
correct), but not indicated as LoTW confirmed.
How can I get Dxbase to stop adding duplicate QSOs to my logbook? This
could easily become a serious mess. How about just generating an error
report during the import process noting the unmatched data but not creating
duplicate QSOs and not overwriting good data with bad?
73,
Bill NT1Y
Topsham VT
_______________________________________________
Dxbase mailing list
Dxbase at mailman.qth.net
http://mailman.qth.net/mailman/listinfo/dxbase