It sounds as if some of your call history file entries may have the state
where the program is expecting to find the IARU zone. As for the failure
to update, Tom is going to look at that tonight (back to work after
vacation). I believe that the program should attempt to guess the zone for
those stations that do not have a zone in the call history file, and
over-ride the guess for those that are included, but will wait and see what
At 07:26 AM 5/31/2005, you wrote:
>You are right. I have ticked Call History Lookup :-))
>I have suspected it might be something wrong in my logger setup.
>Tnx for the help
>----- Original Message -----
>From: "Pete Smith" <n4zr@...>
>Sent: Tuesday, May 31, 2005 12:55 PM
>Subject: Re: [N1MM] IARU zone field values
> > Sam, are you using a call history file?
> > 73, Pete
> > At 06:46 AM 5/31/2005, you wrote:
> >>When NA calls are entered in the call sign field, zone field sometimes
> >>displays states/provinces, sometimes ITU zone numbers which is odd.
> >>N1MM zone value is CT, while the zone value of W3OK is 08.
> >>Another observation is that the change of a call sign doesn't update zone
> >>field with the proper value.
> >>Enter VE7AHA + space. Zone field vaule is 02.
> >>Press space again, going back into call field to correct the call sign
> >>number 7 into 2.
> >>The call sign is now VE2AHA, pressing space doesn't change the zone field
> >>value into 04. It remains 02 forceing the operator to retype it to a
> >>correct value.
> >>Sam, 9a3os