# more AA6YQ comments below
+ Presumably you followed step 1 in
+ and thus can quickly recover.
Of course not
# Mistake 1: always direct DXKeeper to backup your log before initiating an action in the "Modify QSOs" panel.
, BUT I had narrowed the log so that only the QSOs within a time period were shown and then told it to modify QSL_Sent to N. Then it asked if I wanted to Recompute, why?
# Because changing a QSO's "QSL Sent" field can alter its award progress.
No clue, but I said yes.
# Mistake 2: never initiate a function that you don't understand.
Then I got a multipage document of things it changed. When I sent the statement below I thought the Recompute had changed a bunch of Y to N, but that wasn’t the case. It made a BUNCH of changes to I suspect hundreds of QSOs and probably because what it changed corrected stuff that was somehow wrong.
# Yes, as described here:
The biggest thing I think this tells me is maybe I need to do recomputes more often, although I thought I was doing it whenever you made changes to DXKeeper and asked us to recompute.
# That's not correct. When you make changes that might alter your award status for the DXCC, IOTA, Marathon, VUCC, WAS, WAZ, or WPX awards, DXKeeper automatically updates Realtime Award Tracking for those awards without any action on your part (unless you have the "automatically recompute realtime award tracking" option disabled). DXKeeper does this by scanning only the QSOs associated with the change. For example, if you change the mode of a QSO with Iceland, DXKeeper will scan all QSOs with Iceland to update your DXCC award progress with that country, and (if you're pursuing WAZ) scan all QSOs with stations in Zone 40 to update your WAZ award progress with that zone. This "selective recomputation" automatically maintains accurate realtime award tracking for the above awards. "Selective recomputation" does not perform all of the checking, correcting, and reporting provided by the manually invoked Recompute function:
# As with many power tools, careless use of DXKeeper's "Modify QSOs" function can cause significant damage. I've warned you about this several times over the years that you've been using DXLab.
73,
Dave, AA6YQ
