[LOGic] DXCC country names

Mon Apr 9 14:15:06 EDT 2007

Does anyone know a quick way to modify the log form to display not just the
DXCC prefix (which is standard) but also the full country name? I know I can
look it up a million ways to Sunday, but I just wanted it to appear on the
log form automatically. I thought I knew the program pretty well by now, but
I just haven't been able to figure this one out. 

73, de
Marty, N1HT

-----Original Message-----
From: logic-bounces at mailman.qth.net [mailto:logic-bounces at mailman.qth.net]
On Behalf Of logic-request at mailman.qth.net
Sent: Monday, April 09, 2007 4:02 AM
To: logic at mailman.qth.net
Subject: LOGic Digest, Vol 36, Issue 3

Send LOGic mailing list submissions to
	logic at mailman.qth.net

To subscribe or unsubscribe via the World Wide Web, visit
	http://mailman.qth.net/mailman/listinfo/logic
or, via email, send a message with subject or body 'help' to
	logic-request at mailman.qth.net

You can reach the person managing the list at
	logic-owner at mailman.qth.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of LOGic digest..."

Today's Topics:

   1.  Export/Import Problem (Carl J. Denbow)
   2. RE:  Export/Import Problem (mel martin)
   3. RE:  Export/Import Problem (Carl J. Denbow)

----------------------------------------------------------------------

Message: 1
Date: Sun, 8 Apr 2007 17:56:52 -0400
From: "Carl J. Denbow" <n8vz at qth.com>
Subject: [LOGic] Export/Import Problem
To: <logic at mailman.qth.net>
Message-ID: <200748175652.693616 at n8vz-hamshack>
Content-Type: text/plain; charset="iso-8859-1"

I'm having a problem with the LOGic export routine.  When I export to an
ADIF file, the last field is titled "guid" and contains non-ASCII
characters.  ADIF is not supposed to have any non-ASCII fields.  When I try
to import this ADIF file into MixW, it will only export about two records
and then crashes.  Any idea how to stop LOGic from exporting the "guid"
field.  Any idea what it actually is?  I've emailed Dennis about this issue,
but haven't yet received a response.  In the meantime, I thought one of the
learned ones on this list might know what the problem is and what a fix
might be. 

Thanks & 73,

Carl
N8VZ

-- 
Carl J. Denbow, n8vz at qth.com on 4/8/2007

------------------------------

Message: 2
Date: Sun, 08 Apr 2007 19:17:05 -0400
From: mel martin <ve2dc at videotron.ca>
Subject: RE: [LOGic] Export/Import Problem
To: n8vz at qth.com,	'LOGic is open to all radio amateurs for discussion
	of LOGic logging	program' <logic at mailman.qth.net>
Message-ID: <000401c77a34$05894a00$6890a8c0 at STARGATE>
Content-Type: text/plain; charset=us-ascii

Sure go to setup-log fields and turn off ADIF export for guid.

> -----Original Message-----
> From: logic-bounces at mailman.qth.net 
> [mailto:logic-bounces at mailman.qth.net] On Behalf Of Carl J. Denbow
> Sent: April 8, 2007 17:57
> To: logic at mailman.qth.net
> Subject: [LOGic] Export/Import Problem
> 
> 
> I'm having a problem with the LOGic export routine.  When I 
> export to an ADIF file, the last field is titled "guid" and 
> contains non-ASCII characters.  ADIF is not supposed to have 
> any non-ASCII fields.  When I try to import this ADIF file 
> into MixW, it will only export about two records and then 
> crashes.  Any idea how to stop LOGic from exporting the 
> "guid" field.  Any idea what it actually is?  I've emailed 
> Dennis about this issue, but haven't yet received a response. 
>  In the meantime, I thought one of the learned ones on this 
> list might know what the problem is and what a fix might be. 
> 
> Thanks & 73,
> 
> Carl
> N8VZ
> 
> 
> -- 
> Carl J. Denbow, n8vz at qth.com on 4/8/2007 
> _______________________________________________
> LOGic mailing list
> LOGic at mailman.qth.net http://mailman.qth.net/mailman/listinfo/logic

------------------------------

Message: 3
Date: Sun, 8 Apr 2007 20:31:52 -0400
From: "Carl J. Denbow" <n8vz at qth.com>
Subject: RE: [LOGic] Export/Import Problem
To: <ve2dc at videotron.ca>,	LOGic is open to all radio amateurs for
	discussion of LOGic logging	program <logic at mailman.qth.net>,
'LOGic
	is open to all radio amateurs for discussion of LOGic logging
program'
	<logic at mailman.qth.net>
Message-ID: <200748203152.426470 at n8vz-hamshack>
Content-Type: text/plain; charset="us-ascii"

OK, I'll do that.  What exactly is guid? 

On Sun, 08 Apr 2007 19:17:05 -0400, mel martin wrote:
> Sure go to setup-log fields and turn off ADIF export for guid.
>
>> -----Original Message-----
>> From: logic-bounces at mailman.qth.net
>> [mailto:logic-bounces at mailman.qth.net] On Behalf Of Carl J.
>> Denbow Sent: April 8, 2007 17:57 To: logic at mailman.qth.net
>> Subject: [LOGic] Export/Import Problem
>>
>>
>> I'm having a problem with the LOGic export routine.  When I
>> export to an ADIF file, the last field is titled "guid" and
>> contains non-ASCII characters.  ADIF is not supposed to have any
>> non-ASCII fields.  When I try to import this ADIF file into MixW,
>> it will only export about two records and then crashes.  Any idea
>> how to stop LOGic from exporting the "guid" field.  Any idea what
>> it actually is?  I've emailed Dennis about this issue, but
>> haven't yet received a response. In the meantime, I thought one
>> of the learned ones on this list might know what the problem is
>> and what a fix might be.
>>
>> Thanks & 73,
>>
>> Carl
>> N8VZ
>>
>>
>> --
>> Carl J. Denbow, n8vz at qth.com on 4/8/2007
>> _______________________________________________ LOGic mailing list
>> LOGic at mailman.qth.net
>> http://mailman.qth.net/mailman/listinfo/logic
>>
> _______________________________________________
> LOGic mailing list
> LOGic at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/logic
>
>
> __________ NOD32 2173 (20070407) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com

------------------------------

_______________________________________________
LOGic mailing list
LOGic at mailman.qth.net
http://mailman.qth.net/mailman/listinfo/logic

End of LOGic Digest, Vol 36, Issue 3
************************************