[Dxbase] ADIF Import issue

Thu Nov 16 15:24:54 EST 2006

Yes the contest all operates under VE3SY with all QSL cards coming to and sent from VE3SY., To me that meets the license that DXB
issues with the software. In fact I ONLY have one copy of DXB that I use for non-contest operating and for 100% of all of my QSLing
including contests..
The issue is that when I operate a contest in a M/2 or M/M if you keep track of Operators during the test, the Contest software - in
my case Writelog - stores the operator name for each Q. Now when you save the Writelog contest data as an ADIF to import into DXB
these Operator call signs follow.
So this does not seem like a big deal as when you look at the new Qs that have been just imported into DXB all is 100% including,
way over the the extreme right side in the OPERATOR column, you will see the Callsign of the person who was at the controls during
the contest. One still does not expect this to be a AUTHORIZED use issue with the license we bought from DXB, HOWEVER - try now to
reply to QSL cards from this contest. Any Q that was not made by myself ( and out of 4,800 Qs during CQWW I was but 1 of 5 ops)
cannot be printed without going into the database and changing every entry. 
A ludicrous and unnecessary use of the AUTHORIZATION restrictions built into DXB.
Hope you follow the issue now Joe?
73
Paul VE3SY
-----Original Message-----
From: Joe Pontek [mailto:k8jpv31jp at peoplepc.com] 
Sent: Thursday, November 16, 2006 9:25 AM
To: Paul Cassel
Cc: 'Fred Handscombe'
Subject: Re: [Dxbase] ADIF Import issue
Hi Fred & Peter,
I am getting confused with this conversation. Maybe one or the two of you can clear it up for me.
When you operate in a M/2 or a M/M, you use one "station" callsign, right? When you make out 
QSL cards, it is for that callsign, not the operator's callsign.
As, when I bought DXBase, I had it registered for my "callsigns," K8JP, VP5/K8JP, VP5JP, and
V31JP. I am covered.
Now, if I operate with another callsign, say K8MFO or V31YN, I am not covered. A callsign is
the station's identification, not the operator's, though we use it as such. But then, Don or Gerd will
be doing the QSLing for their station's callsigns, not me.
Now, if you operated under your own DXBase licensed callsign, is the issue you want to add the
actual operator's callsign to the label? The way you stated in your original post, it almost sounded
like you used more than one callsign as a M/2 and that is not allowed in M/2 or M/M or M/S.
If I worked you in the CQ WW, the card I want will be for the station, seldom do I care who the
operator is, but if that is of big concern, put that in the comments and that can be placed on the
label, if I remember correctly.
I think, maybe, also, when you did your import, it should have been with the callsign of the "station",
not the operators.
Paul Cassel wrote: 
The issue I see is WHY am I unable to print QSL cards. This makes ZERO SENSE.
Are you saying that because the Callsign field is not mine that I am now unable to use DXBase to print cards without jumping through
hoops?
If the above is true, WHY does DXB allow the field to be imported without a warning?
Based on ramping up my contest operating, I am rapidly seeing that DXB may no longer be the correct logging program for my station.
This is totally unfair to the hundreds of hams requesting QSL cards following a major contest when I operate M/2, M/S or M/M.
JACK
You need to provide a PATCH here ASAP
Paul VE3SY

-----Original Message-----
From: Fred Handscombe [mailto:fredch at homeshack.freeserve.co.uk] 
Sent: Thursday, November 16, 2006 1:01 AM
To: Paul Cassel; 'Peter Dougherty'; dxbase at mailman.qth.net
Subject: Re: [Dxbase] ADIF Import issue
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

______________________________________________________________
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

-- 
Best regards de V31Joe"Palooka"
Joe Pontek, Sr.
26441 Devaney Road
Arcadia, IN 46030-9532
USA
317-984-7388
or
P.O. Box 280
Dangriga
Stann Creek District
Belize
501-520-7072
V31JP K8JP VP5/K8JP VP5JP K8JP/VA2
k8jp at arrl.net
http://mywebpage.netscape.com/v31jp/homepage.html