CT-User
[Top] [All Lists]

[ct-user] Bug in C2A.EXE?

To: <ct-user@contesting.com>
Subject: [ct-user] Bug in C2A.EXE?
From: Jim Reisert AD1C <jjreisert@alum.mit.edu> (Jim Reisert AD1C)
Date: Thu, 9 Mar 2000 18:53:19 -0500
At 06:20 PM 3/9/00 -0500, Rob Kennedy wrote:

>Unlike some other Logging programs, Logger actually checks the contents of
>the State field in the ADIF file when importing the ADIF file into Logger.
>If the state field does NOT contain a valid abbreviation for a US state, the
>record is rejected and it is not imported into Logger.  The rejected records
>are placed in a file called BAD.ADI.

My point was that the importing program (logger in this example) can parse 
the callsign FIRST to determine the country, then if it is NOT USA, it can 
ignore the STATE field.  This is easy for a logging program to do.  It is 
hard for C2A to do because the country information is not stored in the 
.BIN file, and C2A does not contain a callsign parser.

My other point was that other logging programs seem to have no problem with 
this.  It's a trivial amount of code for you (or anyone) to write.  It's a 
NON-TRIVIAL amount of code to write a callsign to country parser.

73 - Jim AD1C


--
Jim Reisert AD1C <jjreisert@alum.mit.edu>
http://people.ne.mediaone.net/ad1c/


--
Submissions:              ct-user@contesting.com
Administrative requests:  ct-user-REQUEST@contesting.com
WWW:                      http://www.k1ea.com/
Questions:                owner-ct-user@contesting.com


<Prev in Thread] Current Thread [Next in Thread>