The WPX award program has some "interesting" rules for computing prefixes
from callsigns; see section 3 in
<>
In particular, note part C of that section: "Example: LX/WN5N would count as
LXO"
To determine what callsigns are responsible for your 1BO and 1KO prefixes,
run the "CQ WPX" panel's Submission report; it lists a callsign for each
prefix. If you think that one or more prefixes have been computing
incorrectly, please let me know and I'll take a look.
73,
Dave, AA6YQ
toggle quoted message
Show quoted text
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Phil
Cooper
Sent: Monday, September 07, 2009 11:43 AM
To: dxlab@...
Subject: [dxlab] A query about the WPX report
Hi again!
After checking my WAC tally, I also decided to check my WPX progress.
After running the report, it produces a nice list of prefixes.
My query is that it shows I have worked prefixes that I cannot find in my
log!
For example, it shows I have worked 1B0 and 1K0, but no such calls exist.
I know I have the right SQL expression, as filtering for a known good call
works OK - I used CY9.
So, how come I end up with prefixes like 1B0 and 1K0 that are clearly not
valid, and do not appear to be in my log?
And one final thought...........
Would it be useful to have a call (or calls??) listed for these prefixes in
the WPX list?
The WPX application form has to show call, date, time, band, mode etc, but
the WPX report doesn't really provide this info.
As I have over 1000 WPX's, it does get a little tiresome having to filter
the log for each WPX, QSL received etc.
73 for now
Phil GU0SUP
---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 090906-1, 06/09/2009
Tested on: 07/09/2009 16:42:58
avast! - copyright (c) 1988-2009 ALWIL Software.
------------------------------------
Yahoo! Groups Links
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.74/2339 - Release Date: 09/07/09
06:40:00
