[Dxbase] ADIF Import issue

Wed Nov 15 20:57:26 EST 2006

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 
>>