Bill,
I sort of thought the problem with the county imports was caused from other
logging programmes doing a less than adequate job of uploading the correct
county name and maybe LoTW for not filtering them properly. I am pretty sure
someone (maybe Jack) once told me that DXBase was 100% accurate on the
county information according to the county hunter's rules.
For Canada, I don't know of any county awards to chase so I simply don't
track them and I just ignore those import reminders. Having said that I am
sure my hands are about to be slapped for saying such. <grin>
As far as Alaska, also Nevada and Virginia goes, I use the following note
to remind me and make the proper changes. I also copy/paste the county given
by the operator in to the QTH field of DXB.
My reminder list:
------
Nevada - Independent Cities do not count as Counties
Virginia - Independent Cities do not count as Counties
Alaska First Judicial District - Southeastern:
Haines
Juneau
Ketchikan Gateway
Prince of Wales-Outer Ketchikan
Sitka
Skagway-Yakutat-Angoon
Wrangell-Petersburg
Alaska Second Judicial District - Northwestern:
Nome
Northwest Arctic
North Slope
Wade Hampton
{This district includes man made oil drilling islands/pads in the Arctic
Ocean}
Alaska Third Judicial District - Southcentral:
Aleutians East
Aleutians West
Anchorage
Bristol Bay
Dillingham
Kenai Peninsula
Kodiak Island
Lake and Peninsula
Matanuska-Susitna
Pribilof Islands
Valdez-Cordova
Alaska Fourth Judicial District - Central:
Bethel
Denali
Fairbanks North Star
Southeast Fairbanks
Saint Matthew Island
Yukon-Koyukuk
-------
There is no doubt DXBase is the best when it comes to logging software and
QSL/Award management.
By-the-way Bill, thanks for the many contest QSO's from your station.
73 Eric - VE3GSI
----- Original Message -----
From: "Bill Parry"
> When I think of all the cool stuff my DXBase does (...still does) I often
> wonder whether it is worth the trouble of upgrading. I am not nearly as
> anxious as some to upgrade to the next greatest version. Everything in my
> DXBase works like it supposed to ...unless I do something stupid like
> screw
> up the .mdb file or lose one of my windows. I am sure hoping that the next
> version is "tried and true" and not something like Microsoft puts out
> hoping
> that the purchasers will trouble shoot for them. I think that is what
> Neal
> is doing.
>
> (Neal you needn't worry, I will be buying the new version when it comes
> out
> and have since DXBase was DOS.)
>
> I do have one little caveat but it doesn't bother me much and that is the
> county function. When I go out to LOTW and download/import my LOTW QSLs I
> always get errors on the KL7s, VEs and a few other minor ones. I know that
> my county stats are wrong because of this. I did my monthly upload of my
> QSOs, followed by my import of new LOTW QSLs yesterday and have a error
> file
> that has a good 25 county errors...all VEs. Since I don't do counties its
> really no big deal but it would be nice if this were fixed so that what
> LOTW
> says is a county, DXBase would say is a county too.
>
> Seems like I remember a discussion about the KL7 counties being a little
> strange, Que Sera. :-)
>
> Bill W5VX
>
______________________________________________________________
Dxbase mailing list
Home: http://mailman.qth.net/mailman/listinfo/dxbase
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
