Brian,
Sorry, I misunderstood what you were looking for in your first query. The
QSL_SENT and QSL_RCVD fields are not included in the ADIF file because they
are not defined fields in the general logger. There is a solution, add the
fields to the logger yourself. Here is a sample ADIF file produced by the
general DX logger after a slight modification.
<PROGRAMID:8>WriteLog
<PROGRAMVERSION:6>11.06A
<EOH>
<QSO_DATE:8>20120828 <TIME_ON:6>145744 <FREQ:8>14.02700 <BAND:3>20m <STX:1>1
<MODE:2>CW
<CALL:5>VK3MI
<APP_WRITELOG_M:1>1
<APP_WRITELOG_20:3> 1
<APP_WRITELOG_COUNTRY:9>Australia
<APP_WRITELOG_C:1>
<APP_WRITELOG_PREF:2>VK
<RST_SENT:3>599
<RST_RCVD:3>599
<APP_WRITELOG_Name:5>BRIAN
<APP_WRITELOG_QSLS:1>Y
<APP_WRITELOG_QSLR:1>N
<EOR>
Note the last two fields now indicate the QSLS and QSLR status. Here is how
to modify the general logger to get the info you want.
In the General DXCC logger click on Contest/Exchange Format Setup... If a
window opens asking you if you want to initialize all fields answer NO. In
the Edit QSO Exchange Fields window click on New and in the Caption box type
a name for the new field, I used QSLS. In the list of check boxes select
Prompt, No Space character allowed and then Save. Now repeat these steps
and add another new exchange field called QSLR. Again click the Prompt, No
Space character allowed check boxes and Save. Now click on OK. When the
window closes you will note the two new fields QSLS and QSLR are in the
Entry window. You may have to scroll the log window to the right to see the
two new fields in the log, but if you checked the Prompt boxes they will
display there. These new fields are editable, just like any other field so
you can update previous log entries if you want. I simply entered Y or N as
the field entry. If desired you could also add a couple more fields for
Date Sent and Date Rcvd, your choice. If you add date fields like this add
a few spaces after the field name in the Caption box to provide the field
width you need.
Once you have the fields created do a Save Configuration so that WL will
retain the fields for the next time you use the General DX logger module.
Now when you create an ADIF the newly created fields will be included in
your file. Good luck.
73,
Gary AL9A
----- Original Message -----
From: "Brian Miller" <brianmiller@xtra.co.nz>
To: <writelog@contesting.com>
Sent: August 28, 2012 5:34 AM
Subject: Re: [WriteLog] QSL Status Missing in ADI Files Exported from
WL(Gary AL9A)
> Thanks Gary
>
> The fields that I am looking for are the ADIF QSL_RCVD and QSL_SENT
> fields.
> It appears that these fields are not exported by the WL general DX logging
> module.
>
> 73, Brian VK3MI ZL1AZE
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 26 Aug 2012 09:03:53 -0800
> From: "Gary AL9A" <al9a@mtaonline.net>
> Subject: Re: [WriteLog] QSL Status Missing in ADI Files Exported from
> WL
> To: <WriteLog@contesting.com>
> Message-ID: <F61B364CDD0C4BF9869E7A0DF0D79E0F@AL9APC>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
> reply-type=original
>
> Brian,
>
> I think it is dependent upon which contest module you are using. In
> looking
> back through some of my recent contest adi files I see that some of them
> have the RST_SENT and RST_RCVD fields included while other contests do
> not.
> Even though most contests require RST as part of the exchange many of them
> do not. In my case when I load my contest adi file into my general
> logger,
> DXBase 2007, the import routine sets the RSTS and RSTR values to the
> default
> of 599. I don't think the lack of these values in the adi file is
> indicative of a problem in WriteLog.
>
> 73,
> Gary AL9A
>
>
> ----- Original Message -----
> From: "Brian Miller" <brianmiller@xtra.co.nz>
> To: <WriteLog@contesting.com>
> Sent: August 25, 2012 6:59 PM
> Subject: [WriteLog] QSL Status Missing in ADI Files Exported from WL
>
>
>>I note that exporting a WL log to ADIF format results in an ADIF file
>>which
>> does not seem to include the QSL status field (e.g., sent and received
>> info)
>> that is held within the WL database.
>>
>> Have others noticed this and/or found a work around?
>>
>> 73
>>
>> Brian VK3MI ZL1AZE
>>
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|