开云体育

I had a LOT of these when I brought old 2001 year satellite qsos in with a sloppy *.adi file. *The grid squares looked "good"*, but until I went into EDIT and deleted the grid square, and then

Lesson Learned: Don't Give Up I imported > 20,000 QSOs a few weeks ago when I "converted" from several different logs (*.adi imports) to a unified DXKeeper log. The "combined" log was a real mess.

+ AA6YQ comments below KQ40ck is working all right. JO28tp on the other hand is not. But when I delete the locator in grid1 field and rewrite it, it looks OK. I am new to this logging program, so I

Den 11.03.2020 01.28, skrev Dave AA6YQ: KQ40ck is working all right. JO28tp on the other hand is not. But when I delete the locator in grid1 field and rewrite it, it looks OK. I am new to this logging

+ AA6YQ comments below I have some broken QSOs with LA9VFA. Error message: invalid gridsquare. This ham operated from two different locators, but call was the same, as an /A or is not recommended in

I have some broken QSOs with LA9VFA. Error message: invalid gridsquare. This ham operated from two different locators, but call was the same, as an /A or is not recommended in Norway. What is the fix

Club Log's call tester is a goo resource for these. https://clublog.org/test.php 73, Mike ND9G

+ AA6YQ comments below I still have some qsos where the DXCC ID is blank, mostly TO#x entities from N1MM.....how can I find those? Are all TO3Z qsos FG? Are all TO0A qsos FS? + No. Any TO or TM

Thanks for your log file and spot database, Markku. The Spot Database entry for KD6DW does not specify a CQ zone, thus SpotCollector did not highlight it as "needed" for WAZ. Take the steps

I still have some qsos where the DXCC ID is blank, mostly TO#x entities from N1MM.....how can I find those? Are all TO3Z qsos FG? Are all TO0A qsos FS?

+ AA6YQ comments below thanks Dave, fixed all 556 broken qsos in a record amount of time !!!! + Good! DXKeeper will help you avoid creating new broken QSOs. 73, Dave, AA6YQ

+ AA6YQ comments below In Spotcollector I have noticed that some callsigns does not have info about their DXGrid (Locator). Why not? + See the " Determining the Location of each Active DX Station"

thanks Dave, fixed all 556 broken qsos in a record amount of time !!!!

+ AA6YQ comments below ahh...so AFTER running the recompute, all the original broken 17m qsos are "fixed"...so should I run recompute after every edit? + If you modify an individual QSO, DXKeeper will

* more AA6YQ comments below So....I started with about 550 broke qsos.....starting at the beginning, I found several, qsos which were originally logged in EQF, 17m qsos where the transmit freq was

ahh...so AFTER running the recompute, all the original broken 17m qsos are "fixed"...so should I run recompute after every edit?

In Spotcollector I have noticed that some callsigns does not have info about their DXGrid (Locator). Why not?

+ AA6YQ comments below I see that you've released a new version of DXKeeper. I've upgraded to it and just rerun the eQSL upload. Everything works fine now. All of the QSO records went through. +

So....I started with about 550 broke qsos.....starting at the beginning, I found several, qsos which were originally logged in EQF, 17m qsos where the transmit freq was 18.000.....I did an sql filter,

They were.? Thanks, Mike. 73,? Jim? W9FI