Jim, My apologies. I stand corrected on AC8H. He does indeed come up with the right info. Is the only solution on these types of calls to have an entry in the callsign table of the both the old and new country?
Jim, KS1j ----- Original Message ----- From: "Jim Reisert AD1C" <[EMAIL PROTECTED]> To: "Jim Bowman" <[EMAIL PROTECTED]>; <[email protected]> Sent: Saturday, February 26, 2005 14:58 Subject: Re: [Dx4win] Country file Question > At 09:54 AM 2/26/2005, Jim Bowman wrote: > > >In examining the Callsigns associated with A5, AC7A does not appear in Ver > >13 but does appear in Ver 15 with a start date of 1/9/1963. I also noted > >that if I entered AC8H (a US call in Ohio) the prefix automatically fills in > >as A5 since he too is in the callsign table for Bhutan. > > > >So assuming DX4WIN imported correctly, why no error on the prefix? Second, > >if AC7A was a legitimate operation in 1963, it appears my only option on > >AC7A is modify the log entries and overwrite the Bhutan prefix and make it W > >again. This, I assume, would generate a callsign table entry in W prefix. Or > >would it be best to add prefix mappings with start and end dates and delete > >the callsign? Or is there a real simple solution? > > Jim, there are some errors in the country file which you of course found. > > AC7A should come up as USA, I will fix this. > > AC8H works correctly here, comes up as USA, Zone 4 starting 01/01/1976 > > These are the actual entries in the country file: > > AC7A,0,A5,01/09/1963 > AC8H,0,A5,01/03/1965 > AC8H,4,K,01/01/1976 > > 73 - Jim AD1C > > > -- > Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 > USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.us > >
