[Dxbase] Import
Bill Parry
bparry at rgv.rr.com
Sun Feb 12 02:11:59 EST 2012
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
More information about the Dxbase
mailing list