Hi Bill, The zone issue is not a new issue. It has been thoroughly discussed recently. It is easily checked with one of the standard reports under log maintenance called checkmyzones.rpt. As to the duplicate QSO issue, I have not heard of that. I wonder if it is the result of a combination of data that was not exact or close enough from the confirmation compared to your log. Generally the LoTW import will not create a entry unless the entry is missing from your log.
If you don't like the idea of separately checking the log zones after importing, then choose the non-detailed version of the adif file when you download it from ARRL. Of course you will loose the other data goodies like Iota, grid, etc. For me, I'll take the errors and fix them after. I would assume that DXbase assumed most people knew where they were on this planet and many people don't. 73, Art W2NRA ----- Original Message ----- From: "William H. Hein" <[EMAIL PROTECTED]> To: "DXbase Reflector" <[email protected]> Cc: "Patton, David NN1N" <[EMAIL PROTECTED]> Sent: Sunday, June 13, 2004 3: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 [email protected] http://mailman.qth.net/mailman/listinfo/dxbase
