[Dx4win] Strange happenings?

N3SL at aol.com N3SL at aol.com
Sun Dec 27 19:57:35 EST 2009


My apologies in advance if this has been reported/discussed.  I don't  
recall such, but then I don't recall near what I used to....
 
I just noticed this when "cleaning up" the database for the end of the  
year.  Running version 8.03.
 
I have several QSOs where a LoTW confirmation is the only confirmation of a 
 particular zone on a particular band - mostly 160 and 6.
 
Even though the QSO is marked as confirmed via LoTW in my log, the  zone 
shows "W" (or "M" in a couple).  I've gone to the trouble of looking  each Q 
up in my LoTW account, and the other station, in every case, has included  
his zone.
 
Manually setting the "Cfnm" via QSL box to "Y" sets the zone as  confirmed. 
 
 
Then, to test this further, I found 3 zones where I had both QSL and LoTW  
confirmations (and the zone marked as "C").  In all three of those,  
changing the QSL rcvd to "N" (and having the LoTW "Cfnm" still = "Y") changed  the 
band/zone box from "C" to "W" or "M".
 
In other words, it appears that a confirmation from LoTW is not setting the 
 band/zone to confirmed.  I am not seeing any setting that might affect  
this, but perhaps that's right in front of my face.  Or, perhaps this is a  
bug?
 
Just reporting it, more than anything.   I can get around it by  manually 
setting the QSL rcvd to "Y" - but obviously shouldn't have to do  that....
 
73 - and Happy New Year to the group!
 
Steve


More information about the Dx4win mailing list