[Dx4win] Logging IOTA - some confusion

[Jim Reisert AD1C]

There may be some confusion with how the IOTA field is filled in when 
logging a QSO.

- if this is the first time you have logged the callsign, DX4WIN may 
fill in the IOTA field automatically if the entity has one or more IOTA 
references.  DX4WIN will fill in the most common ("default") IOTA for 
that entity, i.e. OC-034 for Papua New Guinea, P29 or OC-045 for 
American Samoa, KH8.  That default IOTA is part of the country file, and 
each entity may have only one default IOTA.  Since the IOTA is stored in 
your logbook, future country file updates will not change your log in 
this respect.

- if you have logged the callsign before, and you entered an IOTA with 
that QSO, then when you log the callsign again, DX4WIN will use the IOTA 
from the previous QSO as the IOTA for this new QSO.  It will NOT use the 
IOTA found in the country file.

In either case, DX4WIN may have given you an incorrect IOTA.  It is up 
to you to confirm the correct IOTA with each QSO.

Note that this is the way DX4WIN has always worked, and updating the 
country file does NOT affect the IOTA of any existing QSO in your 
logbook.  In rare cases, I have changed the default IOTA for an entity 
to a more common one (KH8 is one example, OC-077 was changed to OC-045), 
but this only affects the entry of new callsigns in the log.

73 - Jim AD1C

-- 
Jim Reisert AD1C/Ø, <jjreisert at alum.mit.edu>, http://www.ad1c.us