Bill, I think you really need to address the issue of incorrect data to the LoTW folks or to the station that submitted the data since that is the source of the issue you describe and not DXbase. As the old saying goes, "garbage in equals garbage out".
A duplicate QSO in DXbase is defined as same date, time, mode, band, and call. It is absolutely impossible to enter a duplicate QSO as defined here into DXbase. So, what you are no doubt seeing is not dupes, but rather QSOs where either you, or the DX station have entered a different date, time, band, mode, or call. They are treated as entirely different QSOs. As for changes to other data such as CQz, ITUz, IOTA, County, etc.... if you don't want that data changed per the data coming from LoTW, then don't download the details file from LoTW. Instead, get the one that doesn't contain these details. Hope this helps, Courtney ----- 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
