Thanks everyone. I'm using CT9 here, so there's no solution but to
enter the dxpedition in my log as KP5/K5D.
By the way, none of the CT10 solutions will work once the special events
call K5D is re-issued to a state side holder. I guess none of the
logging programs can have it both ways - K5D as a KP5 entity and K5D as
a regular USA entity on different QSO dates.
Rich
Jim Reisert AD1C wrote:
> Did you look at the file for CT10? It's different than the other files.
>
> - Jim
>
> On Sun, Feb 15, 2009 at 7:06 PM, Richard <w3rj@ptd.net> wrote:
>
>> Jim,
>>
>> I looked at these files. As I attempted on my own, they simply add the
>> letters K5D to those listed under the KP5 entity. Doing this will
>> result in logging all real USA calls beginning with K5D, like K5DA,
>> K5DSS, as KP5 and not USA. This is exactly what I want to avoid. Is
>> there a way of listing the exact call K5D and only K5D under the KP5
>> listing to avoid this problem.
>>
>> There also exists the problem that in the future when the call K5D is
>> re-assigned to a US based special events station CT will forever be
>> unable to correctly classify its entity.
>>
>> Rich W3RJ
>>
>
>
_______________________________________________
CT-User mailing list
CT-User@contesting.com
http://lists.contesting.com/mailman/listinfo/ct-user
CT on the web: http://www.k1ea.com/
|