Hi Mike,
I started by making sure I got the same behavior as Bud was. I did.
I looked in the QSO for data that looked "off". Didn't find anything. No
'DC" anywhere in the file. I sorted the file by the "state" field and
sorted the file on "state". Then I removed all duplicates in the
Thanks for posting this to the reflector, Lee. How did you figure out it was
AH6AA, who really is in KH6?
73,
Mike Cizek W0VTT
From: Lee Hallin
Sent: Wednesday, 2 June, 2021 08:49
To: w...@arrl.net
Cc: DX4WIN Reflector ; Jim Reisert AD1C
; Mike Cizek W0VTT ; Paul Van Der
Eijk
Glad it worked for you Bud!
I'm a little surprised that it still was OK when you changed the call back
to AH6AA. In my testing, anytime I would remove AH6AA, the problem went
away and when I reverted back to the original log (that had AH6AA in it), I
would get the gibberish until I removed the
Hi Lee,
Yes, you provided an easy solution.
I searched for AH6AA and changed it to KH6AA, saved it, then exited and
restarted DX4WIN.
The gibberish after WY in the county report was gone and the one worked (W)
in the county summary was gone.
I then searched for KH6AA and changed it back to
4 matches
Mail list logo