[Dxbase] Suggestion for new utility/report

[Joe WA6AXE]

Fred and all:

Fred's email came to me directly - and, I did not notice that he had the
DXbase Reflector on the email also - until Mike sent his email too.

ALL -- The "registered callsigns" is "encrypted" and I can not get to that info
automatedly. This is purposed done by the author.  

The only way that I could possibly make some kind of utility - would be to have
the USER "by hand" type-in the "authorized/registered callsigns" .. but, this
brings in some problems also -- some users do not know where to look for the
"Registered Callsigns" that were in their REG file ..

Sorry - but, this one is not do-able as a fully automated utility.

73 Joe wa6axe

> From: fredch57 at emirates.net.ae
> To: wa6axe at hotmail.com; dxbase at mailman.qth.net
> Subject: Suggestion for new utility/report
> Date: Sat, 19 Feb 2011 12:36:05 +0400
> 
> Hi Joe
> 
> I want to add my thanks fo the support you give the DXbase users!
> 
> I have a suggestion for a new report or utility.
> 
> DXBase uses the "Opr Call" column to "validate" the use of the programme.  I 
> have had many discussions with Jack over the years as to why this is wrong 
> under the licencing conditions in some countries and hopefully something new 
> will be used under the new ownership/SW release.
> 
> The way the OPR call column is used introduces errors into the logs and the 
> way they interact with the likes of Club Log and LOTW.  In fact it was using 
> Club log I have spotted my problem (check it out and join at for free 
> www.clublog.org )
> 
> First the Opr Cal is NOT validated against the valid registered callsigns 
> which it should be.  You can enter anything in the column and you are NOT 
> warned, which seems a little unwise when the column is used later to 
> "validate " the data.
> 
> Second if the Opr call entry is NOT one of the registered callsigns then if 
> you do an ADIF export to LOTW, for example, then that line of data is NOT 
> included in the export file.
> 
> Third if you do an LOTW export and certain lines are excluded, these line 
> ARE marked as sent to LOTW even though THEY HAVE NOT BEEN sent!! How crazy 
> is that?  Maybe you see my disagreemnet with this "method" of validating the 
> user.
> 
> So Joe my request is a report or utility that checks each log line for a 
> valid registered call against the registration file, and flags up any wrong 
> entries in Opr Call column.  If there was a way to open each entry for 
> editing, to undo the errors introduced as above,  or do it automatically, 
> that would be even better
> 
> 73 Fred
> G4BWP - A65BD 
>