[LOGic] a report to check logged prefix against dxcc value

Thu May 24 09:42:24 EDT 2012

There is one big problem with what you propose. The prefix table has 
NOTHING AT ALL to do with awards tracking. It merely causes DXCC, CQ 
Zone, etc to get logged automatically -- most of the time. You could 
delete all of the records out of the prefix table, and LOGic would still 
work. You would have to manually select the country in all cases.
LOGic does not require that every possible call map to the proper DXCC 
country. In many cases this is ambiguous -- the only way to know is to 
ask, then manually log the country (or add that complete call in the 
Prefixes list of the prefix table, then log it).
There is a list of most active stations and their DXCC countries on that 
web site that maintains tables for CT, N1MM etc, but it has no 
historical data or date ranges when a particular entry is active like 
LOGic des. However, I am exploring ways to utilize it to our benefit.
What MAY help you is a report that lists the DXCC prefix with the QSO, 
along with the DXCC description and ADIF number from the DXCC list in 
Tools/Setup/List of Valid Values. (This table IS necessary for DXCC 
tracking).
Tnx & 73,
DH
On 5/22/2012 9:05 PM, K0DAN wrote:
> What would also help is a compilation of, say, the past 5 years one-off
> callsigns and DXCC updates (there's probably dozens, maybe a hundred at
> most?). I would not be opposed to doing a manual checklist (altho using the
> database would sure be better!).
>> I'm pretty sure my PREFIX TABLE is up to date, but I'll bet it doesn't match
> yours. Or other peoples'. There's just little stuff that slips by (e.g.
> Kingman Reef = K). The DXCC tables that Dennis has distributed with LOGIC
> updates have been "good" but not "perfect". That represents one of several
> concerns I have had about upgrading beyond LOGIC 8 (and no slam meant
> towards Dennis, that table is just very elusive and nobody keeps it
> current).
>> I'm close to submitting multi-band DXCC...I have a total of about 320
> entities (all bands, and nearly 100+ on %BDXCC) and I am CERTAIN I'm gonna
> miss one or two just because of these little loopholes. It would be nice to
> be able to send one's PREFIX TABLE to an app that compares fields to a
> known-good/current database (no, I'm not volunteering to maintain it) and
> have that app flag suspicious& contradictory entries. Does STUFF.PRG come
> close to this?
>> 73
> dan
> k0dan
>> -----Original Message-----
> From: Hank Phillips
> Sent: May 22, 2012 02:24 PM
> To: kenb at brookner.com ; logic at mailman.qth.net
> Subject: Re: [LOGic] a report to check logged prefix against dxcc value
>> Have you run fix stuff.prg after insuring your prefix table is up to date
> (under tools -> misc utilities -> fix stuff.prg)? That sorted out a lot of
> my stuff, but for those one-off callsigns like K5K, that might be beyond
> that program's reach. Back your log up and try it - but without an accurate
> prefix table, it probably won't have the information it needs to really "fix
> stuff." Good luck es 73,
>> Hank
> AA4HP
>> -----Original Message-----
> From: logic-bounces at mailman.qth.net [mailto:logic-bounces at mailman.qth.net]
> On Behalf Of ken brookner
> Sent: Tuesday, May 22, 2012 3:08 PM
> To: LOGic at mailman.qth.net
> Subject: [LOGic] a report to check logged prefix against dxcc value
>> hello...
>> i'm running logic8/9 and i've got thousands of q's in the log. over the
> years i've switched my data between logging programs and i know some of the
> entries are not accurate insofar as their dxcc value.. for example, i've
> got some kingman reef contacts that show as "K" for dxcc.
>> what i need is a report that will flag and let me print suspicious entries
> and then i can go through my log, check, and fix what's busted.
> i don't think any of the reports that come with logic will do this.
>> is there a report like this floating around somewhere that i could get a
> copy of? barring that... anyone have a hint on how i might write such a
> report?
>> or, is there another program that i could export my log data to and run this
> kind of a report?
>> thanks
> ken, ky5g
> ______________________________________________________________
> LOGic mailing list
> Home: http://mailman.qth.net/mailman/listinfo/logic
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:LOGic at mailman.qth.net
>> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>>>> ______________________________________________________________
> LOGic mailing list
> Home: http://mailman.qth.net/mailman/listinfo/logic
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:LOGic at mailman.qth.net
>> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>> ______________________________________________________________
> LOGic mailing list
> Home: http://mailman.qth.net/mailman/listinfo/logic
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:LOGic at mailman.qth.net
>> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html