[Dxbase] Re: Dxbase ADIF Import issue

[Paul Cassel]

Hi Garth and thanks for your insight.   Your issues must be compounded by many orders of magnitude.  I know many of the Dxpeditions
that you acted for so my issue seems minor compared to what you must experience.

Even in the contesting side of things- after years of subscribing to Writelog and paying for the annual "upgrade" (bug) fixes, it is
now so unreliable in a network environment that many contest stations are abandoning WL and moving to WinTest.  K3LR has been using
WinTest in a very large Multi/Multi environment with solid results.  It appears that Bell and Whistles sometimes get in the way of
basic operation.  Dxbase possibly needs to provide special security keys for proven contesters who do operate with multiple
operators?

Like yourself, the feature that sold me on DXB was not all of the Bells and whistles but rather the ease of QSL management.  To now
loose that feature as my operating conditions change, is not pleasant to say the least.

Would be interested in other packages you may have tried out.

73
Paul VE3SY

> -----Original Message-----
> From: dxbase-bounces+paul=ve3sy.com at mailman.qth.net 
> [mailto:dxbase-bounces+paul=ve3sy.com at mailman.qth.net] On 
> Behalf Of Garth Hamilton
> Sent: Thursday, November 16, 2006 7:42 AM
> To: dxbase at mailman.qth.net
> Subject: [Dxbase] Re: Dxbase ADIF Import issue
> 
> 
> I have also had this problem and I have used the Comment field to 
> deal with it. Not as convent as the callsign field I admit but it 
> does work. The comment field can be placed on the QSL card as well 
> designed for the contest.
> 
> As a QSL MGR it is a real chore to keep all the callsigns in order 
> and switch logs and registrations. I find too, that you are locked 
> into upgrading constantly as DXBASE staff can not or will not update 
> a key if things change in a version that is not the current one. This 
> one issue is fast turning me off DXBase for use as a QSL MGR. When I 
> started with DXBase it was great but it has become a burden trying to 
> keep all the logs upgraded and the keys up to date. I understand the 
> need to provide for security of the product but I think there has to 
> be another way. (IMHO)  I reduced the number of people I was handling 
> cards for by one third just because of this issue.
> 
> regards
> Garth VE3HO
> 
> At 04:03 AM 11/16/2006, you wrote:
> 
> >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
> 
> 
> ______________________________________________________________
> 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
>