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

Jim jbrannig at verizon.net
Wed May 23 10:05:25 EDT 2012


WOW! Thanks for the link.....

When I converted to Logic 9 I spend hours correcting DX countries.
Clublog found a whole bunch that I missed.

73,
Jim

> If you were to upload you log to Clublog
> https://secure.clublog.org/loginform.php the prefix checking system on
> there will do all of that for you, the log is easily exported in ADIF
> format using the utility provided Logic for that - you can set dates etc
> in the filter option when you want to upload. You'll notice too that
> Clublog will also seek out and correct much of the special event station
> stuff which can be confusing - especially from here in the UK with our
> strange GB call allocation system.
> You will have to manually correct your own Logic log file from the
> 'error list' Clublog will provide - first time of uploading just be
> prepared for quite a list!. I have half a sheet of amendment after every
> contest - particularly badly affected are the EU and Asiatic Russia
> prefix allocations. The French TO prefix stuff is also corrected.
> Lionel
> G5LP
> 
> 
> -----Original Message-----
> From: logic-bounces at mailman.qth.net
> [mailto:logic-bounces at mailman.qth.net] On Behalf Of K0DAN
> Sent: 23 May 2012 02:06
> To: aa4hp at titustek.com; kenb at brookner.com; logic at mailman.qth.net
> Subject: Re: [LOGic] a report to check logged prefix against dxcc value
> 
> 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
> 
> ______________________________________________________________
> 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


More information about the LOGic mailing list