[Dxbase] Fw: Error/Warnings When Importing From Log Windows ADIF File

Jim WA9YSD wa9ysd at yahoo.com
Mon Apr 19 18:04:18 EDT 2010


For state errors like PR it is a country not a state for most programs.  If USA call sign used put KP4/ in front of call or /KP4 in back. Depends on what program you use some will accept both ways.  Get in the habit to put it in front.  Most logging programs accept that.  One of the programs uses \ and not / gets confusing. make these changes once the ADIF is imported into DXBase and not before.

It is a lot of work to make these corrections.   Once you have done a few you will get in the rhythm of things.  I had to do this with many programs I have tried.  No one seams to be the same.  DXBase has it's issues as well in this respect.

VHF stuff above 2M with the band and freq errors I have no idea what to do.  Do what is easyest for you to deal with.
 
Stay on course, fight a good fight, and keep the faith.  Jim K9TF/WA9YSD



----- Forwarded Message ----
From: Jim WA9YSD <wa9ysd at yahoo.com>
To: dxbase at mailman.qth.net
Sent: Mon, April 19, 2010 4:45:12 PM
Subject: [Dxbase] Error/Warnings When Importing From Log Windows ADIF File

What I would suggest is to make a note of the call freq and band for each Error call.  Change the freq and band in Log Windows to an 80M or 160M freq and band.  Once imported into DXBase change it to the proper freq  and band.  Seams to be the easiest way as long as you do not have too many of those.

Keep all the other information the same just change band and freq.  REMEMBER WRITE THE CALLS DATE AND TIME ON A SHEET OF PAPER SO YOU CAN GO BACK AND CORRECT IT.


Stay on course, fight a good fight, and keep the faith.  Jim K9TF/WA9YSD


      


More information about the Dxbase mailing list