Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ct\-user\]\s+ADIF\s+CONTEST

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ct\-user\]\s+ADIF\s+CONTEST_ID\s+field\s+\-\s+what\s+to\s+do\?\s*$/: 3 ]

Total 3 documents matching your query.

1. [ct-user] ADIF CONTEST_ID field - what to do? (score: 1): Author: Jim Reisert AD1C <jjreisert@alum.mit.edu>; Date: Sat, 10 Dec 2005 10:26:28 -0500; In previous versions of C2A (CT to ADIF), I put the CONTEST_ID field in the ADIF file header. This field should have been part of each QSO record. So I changed it. And started getting some complaints; /archives//html/CT-User/2005-12/msg00035.html (8,013 bytes)
2. Re: [ct-user] ADIF CONTEST_ID field - what to do? (score: 1): Author: R Johnson <k1vu@tmlp.com>; Date: Sat, 10 Dec 2005 13:16:19 -0500; Jim: This sounds FB to me. I would prefer to not to have any <CONTEST_ID> embedded in record. So your example #1 would fit my needs, just use C2A in the usual manner. Like "C2A 10M05.BIN" or "C2A RAC; /archives//html/CT-User/2005-12/msg00036.html (10,513 bytes)
3. Re: [ct-user] ADIF CONTEST_ID field - what to do? (score: 1): Author: Jim Reisert AD1C <jjreisert@alum.mit.edu>; Date: Mon, 12 Dec 2005 11:00:02 -0800 (PST); I've received two responses, maybe three. Guess this is too much detail for most people. I will be implementing my numbered proposal below. 73 - Jim AD1C -- Jim Reisert AD1C, 7 Charlemont Court, Nort; /archives//html/CT-User/2005-12/msg00041.html (9,472 bytes)

Current List: 1 - 3
Page: [1]