[Dx4win] Ver 8.01 issues

Paul van der Eijk pvandereijk at cox.net
Sat Aug 8 16:27:29 EDT 2009


Mel (and others)

Or you can wait doing this until I come up with a smarter algorithm!

--Paul, KK4HD


Mel wrote:
> When you re-import you log into an empty file from a DXQ/DXN set... it
> should not double up...
>
> I tried Guy's solution also. I had been using | as a separator... but I
> also had many records with 3 fields... result was a 6 solid hours of
> "fixup"... not something I ever want to do again!
>
>
> Tonno Vahk wrote:
>   
>> It does not work this way Guy!
>>
>> I am also in trouble with the delimiter as I have used space between name
>> and QTH.
>>
>> I have been trying to find way to export the log to change the delimiter but
>> it is impossible with DXQ-QXN export-import because the Notes for This Call
>> gets doubled! Meaning the old values are not replaced whatever you do but
>> anything you import on top of them are added with "/".
>>
>> Even if you export your log, delete ALL QSOs after that and import all the
>> QSOs back then your Notes for This Call get multiplied by two with "/" in
>> between. Crazy.
>>
>> And it is not possible to open a new log file (thus getting rid of the old
>> Notes... data) and import all QSOs there because then you also lose all the
>> Groups list.
>>
>> Thus as far as I have no idea how do change delimiter automatically in ADIF
>> file with my domestic tools like excel etc I don't see any way to accomplish
>> this task without the program being modified to let the user choose the
>> delimiter, better yet logic similar to Excel Text to Columns.
>>
>> What I really need is to be able to split at the first space. As there are
>> often spaces in QTH description (like near Rome or alike).
>>
>> 73
>> Tonno
>> ES5TV
>>
>> -----Original Message-----
>> From: dx4win-bounces at mailman.qth.net [mailto:dx4win-bounces at mailman.qth.net]
>> On Behalf Of ON4AOI
>> Sent: Tuesday, August 04, 2009 6:27 PM
>> To: 'Mel'
>> Cc: dx4win at mailman.qth.net
>> Subject: Re: [Dx4win] Ver 8.01 issues
>>
>> Thats normally fixed in a few minutes
>> In version 7
>> Export your log >>> DX4WIN6
>> THE *.DXN file contains the name and qth, change the delimiter with textpad
>> or similar to IN
>> Save and import
>>
>> Guy ON4AOI
>>
>>     
>>> -----Oorspronkelijk bericht-----
>>> Van: Mel [mailto:ve2dc at videotron.ca]
>>> Verzonden: dinsdag 4 augustus 2009 17:18
>>> Aan: ON4AOI
>>> Onderwerp: Re: [Dx4win] Ver 8.01 issues
>>>
>>> very nice... but I have 25,000 QSOs not formatted that way Guy ;-)
>>>
>>> ON4AOI wrote:
>>>       
>>>> Mel and others
>>>>
>>>> The delimiter in or IN works perfect
>>>>
>>>> So MEL IN STE-MARTINE works 100 %
>>>>
>>>> And will populate Name = MEL and QTH= STE-MARTINE
>>>>
>>>> When you do multiple QSO´s operations - Set Name and Qth
>>>>
>>>> Guy ON4AOI
>>>>
>>>>
>>>>
>>>>         
>>>>> -----Oorspronkelijk bericht-----
>>>>> Van: dx4win-bounces at mailman.qth.net [mailto:dx4win-
>>>>> bounces at mailman.qth.net] Namens Mel
>>>>> Verzonden: dinsdag 4 augustus 2009 17:07
>>>>> Aan: David, K2DBK
>>>>> CC: DX4WIN
>>>>> Onderwerp: Re: [Dx4win] Ver 8.01 issues
>>>>>
>>>>> I would suggest that you not use DX4Win to populate the name and QTH
>>>>> fields then. If Paul doesn't allow a specified delimiter ("," or "|"
>>>>>           
>>> or
>>>       
>>>>> "in") then either Jim will modify one of his programs or I will
>>>>>           
>>> write a
>>>       
>>>>> new one. I already have a program than could do this (To recognize a
>>>>> ","
>>>>> as well as "|" is a one line change) but it works with ADIF which
>>>>> doesn't preserve LotW status for example. I used it to transfer
>>>>>           
>>> DX4Win
>>>       
>>>>> data to another logger I was testing (D4W was better). Jim's
>>>>>           
>>> programs
>>>       
>>>>> work with DXQ which is preferable... so I'm hoping that he might
>>>>>           
>>> hack
>>>       
>>>>> one of his programs if we ask him really nicely ;-)
>>>>>
>>>>> Mel...VE2DC
>>>>>
>>>>> David, K2DBK wrote:
>>>>>           
>>>>>> I'd been using ","  (such as   "David, River Vale") but I can live
>>>>>>             
>>>>> with
>>>>>           
>>>>>> it. I suppose the optimal solution would be to have the user
>>>>>>             
>>> specify
>>>       
>>>>> the
>>>>>           
>>>>>> delimiter, but if I really feel the need I can export my log,
>>>>>>             
>>> massage
>>>       
>>>>>> the data, and re-import it. I'm just happy to have the new version
>>>>>>             
>>>>> out,
>>>>>           
>>>>>> and am anxiously awaiting my version 8 key. :-)
>>>>>>
>>>>>> Mel wrote:
>>>>>>             
>>>>>>> Perhaps he could also delimit on "|"... I don't believe I am the
>>>>>>>               
>>>>> only
>>>>>           
>>>>>>> one using this convention.
>>>>>>>
>>>>>>> re MFSK ... conversion to MFSK16 should be OK as I don't think
>>>>>>>               
>>> MFSK8
>>>       
>>>>>>> is used a lot.... not really an issue here as I can change the few
>>>>>>> QSOS involved manually in less time than it took me to complain
>>>>>>>               
>>>>> about
>>>>>           
>>>>>>> it ;-)
>>>>>>>
>>>>>>> I exported in DX4Win ver 6.03 format. I'll send you the file if
>>>>>>>               
>>> you
>>>       
>>>>>>> like Jim.
>>>>>>>
>>>>>>> Maybe you could make your program QSX & Name fix... I already
>>>>>>>               
>>> wrote
>>>       
>>>>> a
>>>>>           
>>>>>>> program to do this and it works fine... but it works on the ADIF
>>>>>>>               
>>>>> file.
>>>>>           
>>>>>>> If I export/import ADIF I will lose information.
>>>>>>>
>>>>>>> I will send file direct.
>>>>>>>
>>>>>>> Jim Reisert AD1C wrote:
>>>>>>>
>>>>>>>               
>>>>>>>> Regarding name, etc.
>>>>>>>>
>>>>>>>> If you read the on-line help, you'll see that DX4WIN looks for:
>>>>>>>>
>>>>>>>>   <name> in <QTH>
>>>>>>>>
>>>>>>>> MFSK is not a real mode.  Neither is PSK.  PSK was removed from
>>>>>>>>                 
>>>>> this
>>>>>           
>>>>>>>> release, QSOs should automatically convert to PSK31.
>>>>>>>>
>>>>>>>>
>>>>>>>>                 
>>>>>>>>> For QSOs where the Frequency string was "Frequency=N,NNNKHz) the
>>>>>>>>> "Frequency=" was left in the notes field instead of being
>>>>>>>>>                   
>>>>> supressed.
>>>>>           
>>>>>>>> Since that's from an import, Paul can (hopefully) fix this.  I
>>>>>>>>                 
>>> can
>>>       
>>>>>>>> modify my "qsxfix" program to deal with this.
>>>>>>>>
>>>>>>>> I'm curious about the Satellite QSOs.  What export/import format
>>>>>>>>                 
>>>>> did
>>>>>           
>>>>>>>> you use?  Would you be willing to send me the file you tried to
>>>>>>>>                 
>>>>> import
>>>>>           
>>>>>>>> (please ZIP it first)?
>>>>>>>>
>>>>>>>> 73 - Jim AD1C
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Aug 4, 2009 at 8:05 AM, Mel<ve2dc at videotron.ca> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>                 
>>>>>>>>> I exported my ver & data and imported it into ver 8 to verify
>>>>>>>>>                   
>>> the
>>>       
>>>>> data
>>>>>           
>>>>>>>>> converts properly.
>>>>>>>>>
>>>>>>>>> Issues...
>>>>>>>>>
>>>>>>>>> I had a few rejects where the mode was MFSK... should probably
>>>>>>>>>                   
>>>>> convert
>>>>>           
>>>>>>>>> to MFSK16.
>>>>>>>>>
>>>>>>>>> I had over 100 cryptic errors {Satel Mode=X}... These were not
>>>>>>>>> satellite
>>>>>>>>> QSOs and were various modes and bands.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> When extracting Frequency...
>>>>>>>>>
>>>>>>>>> For QSOs where the Frequency string was "Frequency=N,NNNKHz) the
>>>>>>>>> "Frequency=" was left in the notes field instead of being
>>>>>>>>>                   
>>>>> supressed.
>>>>>           
>>>>>>>>> When Extracting Name QTH
>>>>>>>>>
>>>>>>>>> I store my data in the Format"Name| QTH| Notes"
>>>>>>>>>
>>>>>>>>> I would have thought this would have been easy to extract... but
>>>>>>>>>                   
>>>>> the
>>>>>           
>>>>>>>>> entire string ends up in NAME... what delimiter is being used?
>>>>>>>>> Shouldn't
>>>>>>>>> the line break be a valid delimiter?
>>>>>>>>>
>>>>>>>>> Mel, VE2DC
>>>>>>>>> ______________________________________________________________
>>>>>>>>> Dx4win mailing list
>>>>>>>>> Home: http://mailman.qth.net/mailman/listinfo/dx4win
>>>>>>>>> Help: http://mailman.qth.net/mmfaq.htm
>>>>>>>>> Post: mailto:Dx4win at mailman.qth.net
>>>>>>>>>
>>>>>>>>> This list hosted by: http://www.qsl.net
>>>>>>>>> Please help support this email list:
>>>>>>>>>                   
>>>>> http://www.qsl.net/donate.html
>>>>>           
>>>>>>> ______________________________________________________________
>>>>>>> Dx4win mailing list
>>>>>>> Home: http://mailman.qth.net/mailman/listinfo/dx4win
>>>>>>> Help: http://mailman.qth.net/mmfaq.htm
>>>>>>> Post: mailto:Dx4win at mailman.qth.net
>>>>>>>
>>>>>>> This list hosted by: http://www.qsl.net
>>>>>>> Please help support this email list:
>>>>>>>               
>>> http://www.qsl.net/donate.html
>>>       
>>>>> ______________________________________________________________
>>>>> Dx4win mailing list
>>>>> Home: http://mailman.qth.net/mailman/listinfo/dx4win
>>>>> Help: http://mailman.qth.net/mmfaq.htm
>>>>> Post: mailto:Dx4win at mailman.qth.net
>>>>>
>>>>> This list hosted by: http://www.qsl.net
>>>>> Please help support this email list: http://www.qsl.net/donate.html
>>>>>           
>> ______________________________________________________________
>> Dx4win mailing list
>> Home: http://mailman.qth.net/mailman/listinfo/dx4win
>> Help: http://mailman.qth.net/mmfaq.htm
>> Post: mailto:Dx4win at mailman.qth.net
>>
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html
>>
>>
>>     
> ______________________________________________________________
> Dx4win mailing list
> Home: http://mailman.qth.net/mailman/listinfo/dx4win
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Dx4win at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com 
> Version: 8.5.392 / Virus Database: 270.13.47/2290 - Release Date: 08/08/09 06:10:00
>
>   


More information about the Dx4win mailing list