This may effect some reports. When checking and downloading LoTW qsl's, I've found a slight problem. I doubt there is a way of fixing this.
Some stations upload their ENTIRE log, each time they submit to LoTW. Instead of just sending in qso's since the last upload, they just send the whole log again. LoTW sees this as a 'update' and overwrites the old qso/qsl with the new qso/qsl even though there is no change in the info. Now when I download qsls, and I do this with a 'since last download' modifier, I get the same qso/qsl, but with a new download date. Consequently, when I import these new qsls into DXB, it changes the LoTWRecieveDate to the new date. If I run some of the new Joe Glockner reports, it indicates that the qsl, was just qsled. This is of no MAJOR concern, it just skews the qsl data a bit as to when uploaded and when qsled. Possibly DXB could process a qsl and if it's already been qsled via LoTW with the exact same data, leave the date of the previous qsl date. Hope that's clear. :-) I also saw an anomaly if you click on 'ANY' in the Lotw Download Report menu box. As I have 13 callsigns on my certificate, it seems to import all of them into my DXBase log...but I can't see them, while the qso numbers indicate that the log file is larger... I will test this a few more time to get the details correct. (I have 'safety backups' made before making these tests to which I can compare logs with). While I'm not superstitious, I just realized that having 13 callsigns might be why I've not won the MegaLotto yet... I better take on a new station to qsl manage. ----------------------------------------------------- Ever stop to think... and forget to start again? ----------------------------------------------------- Bill H. in Chicagoland
