[Dxbase] A few LoTW reminders

[George Johnson]

Hi Fred,
If I read your comments correctly, your observation is similar to what we 
"used" to have in the US for logging requirements.  That is, we had a 
"station log".  All the the requirements you mentioned were also part of 
our recording requirements also...  maybe this makes me very long in tooth...

But I believe your application of DXBase would be resolved quite properly 
by considering any one of your (station) logs to be a DXBase log.  I happen 
to use multiple mdb files for that purpose.  I gather that Bill, W9OL, 
might use a single file with multiple (station) callsigns for his purpose.

Then Jack, on behalf of DXBase, simply requires each of your (station) 
callsigns to be recognised by his registration process which is something 
you also require for your log records.  Added "guest operators" are simply 
notes in the log whether paper or computer.  They do not belong in the 
(station) callsign column in the DXBase log.

IMHO this might give you the proper logging solution while also keeping 
your computer records in a DXBase format that permits QSLing etc.  The note 
column can contain any special information.

Hope this helps,
73, George .. W1ZT



At 01:08 PM 10/19/2005, Fred Handscombe wrote:
>>1. Probably your log contains qso's while using a number of different calls.
>>(I had my novice call, my Advanced call, and now my Vanity call)
>>Each of these callsigns requires that it be included in the .reg file 
>>that you obtain from DXBase upon purchase/renewal.
>>
>>2. Each call in your log must be in the Operator Callsign field during 
>>the proper date timeframe.
>
>I think there is a BIG difference in interpretation outside the US as 
>"our" system does not work like this (above)
>
>1- The logbook (and computor file) is for ONE callsign used on the air, I 
>have multiple lookbooks for each of the callsigns I have and use.  I 
>believe this is the UK licence requirement to have each callsigns logbook 
>in a discrete file (No, I havent read the "rules" carefully in a long time)
>
>2 - This may be specific to the UK.  I am not obliged to enter MY call if 
>I operate my own station.  However if another ham operates my station with 
>my callsign I am obliged to note this in the log.  This is my 
>interpretation of the "operator callsign" meaning the person operating for 
>that QSO.  By default my own call is the operator to "fill the box" with 
>something otherwise which is no big deal.
>
>The nett result of this, and this is where in my opinion DXbase is very 
>wrong, is that I CANNOT send QSL cards using DXbase for any legitimate 
>contacts made from my station(s) by another operator.  The field in the 
>label select which says use "*" for all actually means "all registered 
>callsigns" which is a different thing.  So in fact I need to register ALL 
>the station operators I have ever had and get new registrations each time 
>a new person operates!  This will keep Jack busy!
>
>The problem I have is that I am managing stations which have had many 
>operators and cannot get the DXbase to print cards unless I register every 
>operator.  This seems to be a "new" (and totally unwanted) feature in 2006 
>as I have not had any problems with prior versions.
>
>I respect Jack's right to protect his programme but this is not the way to 
>do it!
>
>But I need a proper solution!
>
>73 Fred
>G4BWP
>
>
>
>
>______________________________________________________________
>Dxbase mailing list
>Home: http://mailman.qth.net/mailman/listinfo/dxbase
>Help: http://mailman.qth.net/mmfaq.htm
>Post: mailto:Dxbase at mailman.qth.net