[Dx4win] Count anomaly

[J. F. Samuels]

I had the same kind of problem -- appeared to be a 40 meter CW QSO -- 
couldn't find it and finally gave up - wasn't important enough to spend more
time looking for it, and never decided which version was right!

John, K2CIB
----- Original Message ----- 
From: "D R Hutchison" <msg.que at NTLWORLD.COM>
To: <dx4win at mailman.qth.net>
Sent: Tuesday, June 22, 2004 7:42 PM
Subject: [Dx4win] Count anomaly


> Whilst checking DXCC Summary status I have discovered a count problem
> between v 5.03 and 6.03.
> Using the same log, with identical date selection parametrs, the Summary
> reports differ by one confirmed QSO, apparently a CW contact. The number
of
> confirmed CW QSOs is reported to be the same under both versions.
> Version 5.03 says 54 worked and 13 confirmed while 6.03 says 55 worked and
> 12 confirmed. Even taking things to a band level, 14Mhz is where the
problem
> seem to lie but again the number of confirmed QSOs is the same on both
> versions and the reports begin and end with the same log entries.
> Not that it is important at this stage, has anyone else encountered
similar
> apparent discrepancies and if so what solution was applied? Needless to
say
> I cannot find the offending QSO.
> The Summary numbers are the same in all other respects, just v 5.03 says I
> have 1 more confirmed?
>
> Also noted that a v 5.03 entry MM/PA3GIO (GM), was converted as an error
on
> 6.03 with a PA prefix. Entry as a new QSO on 6.03 did produce a GM prefix.
>
> Douglas, GM7SVK
>
> _______________________________________________
> Dx4win mailing list
> Dx4win at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/dx4win
>