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 "State" field. There were 51 remaining records with the 51st one being 2 blanks. At this point, I decided to remove all records that didn't have a "state" present. Did this with an F8 with a "state" value of "!*" (all empty state fields). This confirmed (to me) that the issue was not an issue with the "state" value. At that point, I restored to the original file and, starting with AK, removed a state at a time; saved the log file, re-opened the log file and then looked for the gibberish. If I found it, I would go to the next state and repeat the scenario. Eventually I got to HI. When I removed "HI" QSOs, the gibberish went away! I restored the original log again. Now I removed, one county at a time, all QSOs that had a "county" present. This left 19 QSOs. I then started deleting each QSO, one at a time, until the gibberish went away. Removing the AH6AA QSO got rid of the gibberish! I thought I had seen in the past that there were AHxxx calls that were not US calls. Just for grins, I changed the call from AH6AA to KH6AA. The gibberish went away! I was done! :) All the above took several hours and probably over 100 SAVE and re-openings of the log! 73, Lee N7NU On Wed, Jun 2, 2021 at 6:52 AM Mike Cizek W0VTT <mgci...@gmail.com> wrote: > 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 <hall...@lanecc.edu> > Sent: Wednesday, 2 June, 2021 08:49 > To: w...@arrl.net > Cc: DX4WIN Reflector <DX4WIN@mailman.qth.net>; Jim Reisert AD1C < > jjreis...@alum.mit.edu>; Mike Cizek W0VTT <mgci...@gmail.com>; Paul Van > Der Eijk <pvandere...@gmail.com> > 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 AH6AA in it), I > would get the gibberish until I removed the AH6AA. > > > > I am glad everything is OK now and hope it continues to be! > > > > 73, > > Lee N7NU > > > > On Wed, Jun 2, 2021 at 3:04 AM Bud Governale <w3ll...@gmail.com <mailto: > w3ll...@gmail.com> > wrote: > > 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 AH6AA and saved it. > > I exited and restarted DX4WIN. > > The gibberish after WY in the county report remained gone and the one > worked (W) in the county summary remained gone. > > > > I did not use your attached w3ll_new.zip file. > > > > Thanks Lee for spending the time to find an easy workable solution. Much > appreciated to Jim, Mike and Paul for their time. > > > > 73, > > > > Bud W3LL > > > > > > > > On Wed, Jun 2, 2021 at 4:05 AM Lee Hallin <hall...@lanecc.edu <mailto: > hall...@lanecc.edu> > wrote: > > Hi Bud, > > > > Well it took several hours but I think I figured it out (not sure why > though). If you search for call AH6AA on 5-30-21 and change the call (to > test my theory, I changed it) to KH6AA and save it. Exit DX4WIN and then > go back in. Try doing the County -> Listing and you should NOT get the > garbage line at the bottom. > > > > I "think" some AHxxx calls are not in the USA and I'm guessing AH6AA is > one of those. I'm guessing somehow that call throws DX4WIN off when doing > the tallying for counties. > > > > I attached w3ll_new.zip which contains w3ll_new2.dxl. I tried to make the > name unlikely to match a .dxl file you already have. This w3ll_new2.dxl > has the AH6AA call changed to KH6AA. To check it out, you can open the > w3ll_new2.dxl file directly (once unzipped) with DX4WIN. > > > > Let me know if the new file fixes the issue you were having. > > > > 73, > > Lee N7NU > > > > > > > > > > > > > > > > On Tue, Jun 1, 2021 at 5:50 PM Lee Hallin <hall...@lanecc.edu <mailto: > hall...@lanecc.edu> > wrote: > > Hi Bud, > > > > Good news (kinda) -- I get the same results that you saw. > > > > So far I haven't found any "bad" state values. I'll do more digging... > > > > Lee N7NU > > > > On Tue, Jun 1, 2021 at 5:29 PM Bud Governale <w3ll...@gmail.com <mailto: > w3ll...@gmail.com> > wrote: > > Hi Lee, > > > > Thanks for the offer to find and fix the problem. > > Attached is the zipped dxl file. > > > > 73, > > > > Bud W3LL > > > > On Tue, Jun 1, 2021 at 8:15 PM Lee Hallin <hall...@lanecc.edu <mailto: > hall...@lanecc.edu> > wrote: > > Hi Bud, > > > > If you want, send me the .DXL file and I'll see what I can find. > Shouldn't take long to find the culprit. If you send it tonight, I'll send > it back later tonight or tomorrow. > > I can look at the data many different ways so I should be able to find the > problem and fix it (or at least delete it). > > > > 73, > > Lee N7NU > > > > On Tue, Jun 1, 2021 at 12:08 PM Bud Governale <w3ll...@gmail.com <mailto: > w3ll...@gmail.com> > wrote: > > 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 <pvandere...@gmail.com > <mailto:pvandere...@gmail.com> > > wrote: > > > 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) > > > > --Paul > > > > On Mon, May 31, 2021 at 1:09 PM Bud Governale <w3ll...@gmail.com > <mailto:w3ll...@gmail.com> > wrote: > > > >> 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 <mailto:w...@arrl.net> > >> > >> On Mon, May 31, 2021 at 11:06 AM Bud Governale <w3ll...@gmail.com > <mailto:w3ll...@gmail.com> > wrote: > >> > >> > 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 < > >> jjreis...@alum.mit.edu <mailto:jjreis...@alum.mit.edu> > > >> > wrote: > >> > > >> >> 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 <w3ll...@gmail.com > <mailto:w3ll...@gmail.com> > > >> wrote: > >> >> > > >> >> > 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 showing W2JQZ, State NY > and > >> no > >> >> > county listed. > >> >> > > >> >> > How do I remove the state after state WY? > >> >> > > >> >> > 73, > >> >> > > >> >> > Bud W3LL > >> >> > w...@arrl.net <mailto:w...@arrl.net> > >> >> > ______________________________________________________________ > >> >> > DX4WIN mailing list > >> >> > Home: http://mailman.qth.net/mailman/listinfo/dx4win > >> >> > Help: http://mailman.qth.net/mmfaq.htm > >> >> > Post: mailto:DX4WIN@mailman.qth.net <mailto:DX4WIN@mailman.qth.net> > > >> >> > > >> >> > This list hosted by: http://www.qsl.net > >> >> > Please help support this email list: > http://www.qsl.net/donate.html > >> >> > >> >> > >> >> > >> >> -- > >> >> Jim Reisert AD1C, <jjreis...@alum.mit.edu <mailto: > jjreis...@alum.mit.edu> >, https://www.ad1c.us > >> >> > >> > > >> ______________________________________________________________ > >> DX4WIN mailing list > >> Home: http://mailman.qth.net/mailman/listinfo/dx4win > >> Help: http://mailman.qth.net/mmfaq.htm > >> Post: mailto:DX4WIN@mailman.qth.net <mailto:DX4WIN@mailman.qth.net> > >> > >> This list hosted by: http://www.qsl.net > >> Please help support this email list: http://www.qsl.net/donate.html > >> > > > > > > -- > > ~~~~~~~~~~~~~~~~~~~~~ > > DX4WIN logging software > > Paul van der Eijk, KK4HD > > BrookHill Data Systems LLC > > http://www.dx4win.com > > > > > ______________________________________________________________ > DX4WIN mailing list > Home: http://mailman.qth.net/mailman/listinfo/dx4win > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:DX4WIN@mailman.qth.net <mailto:DX4WIN@mailman.qth.net> > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > > ______________________________________________________________ > DX4WIN mailing list > Home: http://mailman.qth.net/mailman/listinfo/dx4win > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:DX4WIN@mailman.qth.net > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > ______________________________________________________________ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:DX4WIN@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
