[Dx4win] DX4WIN Worked Cutoff Problem

[Jim Johns]

Jim -

Thanks.  It was the operation of double-clicking on the W in the report
that I didn't fully understand.  I thought that the report was linked to
the DXCC record QSO.  I didn't realize that it worked the same as using
F8.  Looking closer, the 1988 QSO was just the earliest QSO that matched
the country / band filter and there were QSO's that fell within the Worked
Cutoff Limit.  Reducing the Worked Cutoff to 30 days (which is less than
the most recent QSO date) eliminated the Worked flagged QSO's.

Thanks for the info and for keeping up all of the DX4WIN support files.

73

Jim KA0IQT

On Mon, Jun 10, 2013 at 8:21 PM, Jim Reisert AD1C <jjreisert at alum.mit.edu>wrote:

> On Mon, Jun 10, 2013 at 5:53 PM, Jim Johns <ka0iqt at gmail.com> wrote:
>
> > When I do a Reports:DXCC:Listing (or a Reports:DXCC:Listing Worked) and
> > look at the matrix, I find that I have entries, that when I double click
> on
> > the W symbol, pulls up QSO's from 1998 and 2007 which is way before the
> > cutoff.
>
> Double-clicking on a 'W' in the listing only sets up a filter (same as
> F8), it has no knowledge of the cutoff date.
>
> Here's where it *would* matter.  Say your only QSO with 3B9 was over
> two years ago.  If you have a worked cutoff of 0, or some value > 2
> years, this would show up as a 'W' in your DXCC listing (it has been
> worked within your worked cutoff limit).  If instead you have a worked
> cutoff of some value < 2 years, then it would be outside your worked
> cutoff limit, and there would be NO character in the DXCC listing, as
> if it were never worked.
>
> Does this make sense?
>
> --
> Jim Reisert AD1C, <jjreisert at alum.mit.edu>, http://www.ad1c.us
>