OK, I'm going nuts here. For some reason the "logic" used in creating
selections in a number of places in DX4WIN just never matches what I
expect. I've read the help files and the users manual - they don't help
at all. I'm setting up selections for my two callsigns for LoTW exports.
The first one got set up by accident somehow in the many attempts I made
to do it. But now I can't do the same for a 2nd selection. As soon as I
start to change the selection name, the "Update" button disappears, and I
can't make any other changes to the selection type, etc. Can anyone give
me the sequence of events used to set up a new selection? Many thanks in
advance.
73, Duane
--------------------------------------
Duane Calvin, AC5AA
Austin, Texas
http://home.austin.rr.com/ac5aa
From [EMAIL PROTECTED] Sun Jun 27 21:06:24 2004
From: [EMAIL PROTECTED] (Duane A Calvin)
Date: Sun Jun 27 21:15:48 2004
Subject: [Dx4win] Help on selections definitions
Message-ID: <[EMAIL PROTECTED]>
NEVER MIND! I found the problem - it's apparently a DX4WIN bug. Start
your selection name with an A (or an AC), like my callsign, and it will
not allow you to save that selection name. Don't know why. I started it
with a blank, then went back and deleted the blank after I had everything
else set and it saved it just fine. Weird. Paul, you might want to
check this out.
73, Duane
--------------------------------------
Duane Calvin, AC5AA
Austin, Texas
http://home.austin.rr.com/ac5aa
From [EMAIL PROTECTED] Sun Jun 27 22:23:39 2004
From: [EMAIL PROTECTED] ([EMAIL PROTECTED])
Date: Sun Jun 27 22:33:09 2004
Subject: [Dx4win] LoTW import problems
Message-ID: <[EMAIL PROTECTED]>
I noted this 2 weeks ago, but thought perhaps I'd done something wrong.
Then, I just did another import of new QSLs from LoTW (lotwreport.adi) today,
representing new confirmations during the past 2 weeks.
The adi file has 33 confirmations in it. DX4Win says it successfully
imported 19. Those "missing" 14 indeed are in DX4Win, but every one of them
is a
duplicate QSO now. My original DX4Win entry is there with the upload flag
set, the date set, but Upl Cnf = N. The second log listing (obviously created
by the import process) has the upload flag = N, no date, but Upl Cnf = Y. I
can see no rhyme nor reason in the Qs or the adi file.
Has anyone else seen this, or know what I'm doing wrong or what the problem
is? I am using the ADIF import, with "Imported QSO sets Upload Confirmed
flag" selected.
----------
BTW, LoTW sets Canadian provinces in the <STATE:2> line, and DX4Win gags on
these. Any fix?
Thanks in advance,
Steve
From [EMAIL PROTECTED] Sun Jun 27 22:59:13 2004
From: [EMAIL PROTECTED] (Jim Reisert AD1C)
Date: Sun Jun 27 23:08:33 2004
Subject: [Dx4win] LoTW import problems
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
At 10:23 PM 6/27/2004, [EMAIL PROTECTED] wrote:
>BTW, LoTW sets Canadian provinces in the <STATE:2> line, and DX4Win gags on
>these. Any fix?
Yeah, the ARRL should not do this. Send mail to their LoTW help
address. They need to fix their software.
73 - Jim AD1C
--
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.com
PGP Fingerprint: D8E2 3D78 339F A7F1 8C13 1193 B5D1 4FB6 79D1 70DC
