[Dxbase] ADIF Import issue
Fred Handscombe
fredch at homeshack.freeserve.co.uk
Thu Nov 16 01:00:31 EST 2006
Paul
I have had this boring exchange with Jack in the past. I am afraid he does
not use the term "operator callsign" in the same sense as we do in UK, or as
you do in Canada it seems.
I wanted to request a file from Jack with every operator that uses the
callsigns I keep the log for and then he conceded it was a less good idea!
In the UK ANY licenced operator can use my station and I need to log who it
was (for the rest of this year as we are relaxing logging conditions next
year), so I need many, many "operators" to be authorised with my DXbase.
But the solution is easier than you think as there is a "find and replace"
tool under "edit". Get the log book in focus and run that, replacing the
operators with your own callsign, it only took me a few minutes to clean up
all the logs I had. Rind and replace also works in the panding label data
window too.
The interesting fact was that "operator call" had existed for many DXbase
versions but it only started work in 2005 or 2006 when I faced the same
issues you have described.
73 Fred
G4BWP
----- Original Message -----
From: "Paul Cassel" <paul at ve3sy.com>
To: "'Peter Dougherty'" <w2irt at comcast.net>; <dxbase at mailman.qth.net>
Sent: Thursday, November 16, 2006 1:57 AM
Subject: RE: [Dxbase] ADIF Import issue
Well with almost 5,000 Q from CQ WW weekend and with me suffering from
laryngitis, there were very few Qs in my call so that is not
practical. What I am doing is for each received card that a reply entry is
made, I need to go in and edit EACH AND EVERY record in
the queue database which is by itself a major task
QUESTION
Why will DXB ignore operator call signs when the *wildcard is used?
Why does DXB allow an Unauthorized Call to be imported?
This in my mind is a BUG that needs to be addressed
Paul VE3SY
> -----Original Message-----
> From: Peter Dougherty [mailto:w2irt at comcast.net]
> Sent: Wednesday, November 15, 2006 7:01 PM
> To: Paul Cassel; dxbase at mailman.qth.net
> Subject: Re: [Dxbase] ADIF Import issue
>
>
> At 05:45 PM 11/15/2006, Paul Cassel wrote:
>
> >I am a contester and this past CQWW SSB I operated M/2. Each
> >computer (using WriteLog) logged the operator call signs. When the
> >ADIF file was created and imported to DXB it properly brought over
> >everything INCLUDING the call of the operator.
> >
> >Here's the issue
> >
> >Normal label printing for QSL cards do not find the records as the
> >Callsign is not mine.
>
> DX Base's registration is keyed to that field, unfortunately (it's
> one of the things I disagree with for precisely this reason). My club
> has many operators in Field Day and we wanted to use that field to
> identify who was at the mic or key at any time, and we ran into the
> same issue. I think the only thing you can do is go in and change all
> the entries to your callsign. Speaking personally, I hope Jack can
> come up with a new security model for future releases that allows any
> value to be in that field.
>
>
>
> Cheers,
>
> Peter,
> W2IRT
>
>
______________________________________________________________
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
More information about the Dxbase
mailing list