t;
> 73,
>
> Mike Cizek W0VTT
>
>
>
> From: Lee Hallin
> Sent: Wednesday, 2 June, 2021 08:49
> To: w...@arrl.net
> Cc: DX4WIN Reflector ; Jim Reisert AD1C <
> jjreis...@alum.mit.edu>; Mike Cizek W0VTT ; Paul Van
> Der Eijk
> Subject: Re: [Dx4win] Cou
Subject: Re: [Dx4win] County Report State After WY
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
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
> Both the State and County reports show states in alphabetical order.
> I looked at every state listed in both reports and cannot see a DC state.
Bud, I don't think that's what Paul meant.
In the QSO window, use the Sort menu to sort by State. Use
control-END to look at the last few QSOs in
Hi Paul,
Both the State and County reports show states in alphabetical order.
I looked at every state listed in both reports and cannot see a DC state.
73,
Bud W3LL
On Mon, May 31, 2021 at 10:28 PM Paul van der Eijk
wrote:
> Bud,
>
> Open the logbook window
> select report
> pick a report
Bud,
Open the logbook window
select report
pick a report that will show the state field
sort by state
You should be able to the suspicious state in that sorted list;
most likely it is DC
(a previous version allowed DC to be imported as a valid state;
most likely produced by a contest program)
I deleted W2JQZ. That did not solve the problem. The gibberish W is now
W1ONK.
W2JQZ was the first QSO in the log out of 340,731.
W2JQZ was deleted.
Now W1ONK is the first QSO in the log.
It does not appear to be a DC State issue.
How do I fix the problem?
73,
Bud W3LL
w...@arrl.net
On Mon,
Reports>WAS>Listing>OK
The listing ends at WY. No DC.
F8>Enter DC in State box>enter
Result is no matching qso found.
A restart of DX4IN does not fix the problem.
On Mon, May 31, 2021 at 10:40 AM Jim Reisert AD1C
wrote:
> You probably have a "DC" in one of your State fields. Remove it.
>
You probably have a "DC" in one of your State fields. Remove it.
Save your log. Re-start DX4WIN
On Mon, May 31, 2021 at 5:48 AM Bud Governale wrote:
>
> Issue with County>reports>Listing
>
> The Reports>County>Summary shows a 1 (one) in Worked Mixed.
> Go to Reports>County>Listing:
> After the
Issue with County>reports>Listing
The Reports>County>Summary shows a 1 (one) in Worked Mixed.
Go to Reports>County>Listing:
After the state WY there is a line for the next state. The state is blank,
the county is gibberish and a W in the Mix column.
Clicking on the W opens the Entry window
11 matches
Mail list logo
