[LOGic] Reporting "no QSL status" QSOs with unconfirmed
DXCCentities
Julio Peralta
jperalta at tampabay.rr.com
Mon Dec 3 17:23:31 EST 2007
The term you used unworked means just that! They are un worked. If they
aren't worked they won't show up in your log and there for can't be
searched for. I must be missing something.
Julio, W4HY
-----Original Message-----
From: logic-bounces at mailman.qth.net
[mailto:logic-bounces at mailman.qth.net] On Behalf Of J. Wolf
Sent: Friday, November 30, 2007 5:14 PM
To: LOGic is open to all radio amateurs for discussion of LOGic logging
program
Subject: [LOGic] Reporting "no QSL status" QSOs with unconfirmed
DXCCentities
Here's a new problem for the group's consideration:
Over time, I've accumulated around 550 QSOs that have NO QSL status
recorded. This is largely because I was using another logging program
for
several years and only recorded QSLs that were actually sent and
received.
It turns out that, among these 550 QSOs, there are several unique DXCC
entities but I don't know what they are (LOGic's DXCC report summary
only
says that I have about 6 unique entitites with no status recorded. Now,
I
can (and probably will) go through all 550 contacts to find them, since
THAT
report is easy to generate. What I'd like, however, is to be able to run
a
report that selects for QSOs that not only have no QSL status entered
(that's easy) but, also, that are otherwise unworked DXCC entities. Does
anyone know how to set up and expression that will pull these 6 QSOs out
of
the 550?
--Jeff, K6JW
_______________________________________________
LOGic mailing list
LOGic at mailman.qth.net
http://mailman.qth.net/mailman/listinfo/logic
More information about the LOGic
mailing list