I should further point out that the problem stems from the fact that DxBase2005 (I upgraded to DxBase2006) truncated the seconds. The ADIF time output in DxBase2005 (and earlier I presume) had <TIME_ON:4> instead of <TIME_ON:6>. Although I upgraded from DxBase2005 in 2005, all the uploads created back then seem to be a problem.
>-----Original Message----- >From: [email protected] [mailto:[email protected]] >On Behalf Of Ed K1EP >Sent: Sunday, March 29, 2009 10:08 AM >To: [email protected] >Subject: [Dxbase] DxBase - LoTW Problem > >LoTW allows one to upload any ADIF log, such as one from a contest >program or from DxBase/ When LoTW first came out, I tried loading >each contest ADIF output into LoTW and quickly realized that it would >be easier to load the contests into DxBase first and then >periodically upload the DxBase ADIF output into LoTW. This works >just fine, until you want to download your LoTW QSLs into >DxBase. Why? Because when DxBase imports ADIF contest logs, it >truncates seconds on the QSO time. Contest log ADIF outputs have >HH:MM:SS, but DxBase time converts it to HH:MM:00. So, if you have >uploaded an ADIF log directly from your contest program into LoTW and >then try to match up a QSL with the downloaded report from LoTW, you >get error messages like (the call has been changed to WA1ABC): > >ERROR: WA1ABC The changes you requested to the table were not >successful because they would create duplicate values in the index, >primary key, or relationship. Change the data in the field or fields >that contain duplicate data, remove the index, or redefine the index >to permit duplicate entries and try again. WA1ABC 20050220 >192900 20m CW 599 599 > >The QSOs do not match up because the times are now different. So, I >created a new ADIF file from DxBase to upload to LoTW that would >overwrite the old logs. The original contest ADIF file that was both >uploaded to LoTW and DxBase looked like: > ><CALL:6>WA1ABC <QSO_DATE:8>20050220 <TIME_ON:6>192939 <MODE:2>CW <BAND:3>20M ><FREQ:6>14.094 <RST_SENT:3>599 <RST_RCVD:3>599 <RX_PWR:3>100 <EOR> > >The new ADIF file from DxBase to upload looked like: > ><CALL:6>WA1ABC <QSO_DATE:8>20050220 <TIME_ON:6>192900 <RST_SENT:3>599 ><RST_RCVD:3>599 <QSL_VIA:4>None ><ITUZ:2>28 <OPERATOR:4>K1EP <PFX:3>HB9 <QSL_RCVD:1>N <DXBQSL_RCVD:1>0 ><FREQ:8>14.09400 ><BAND:3>20M <CQZ:2>14 ><MODE:2>CW <QSL_SENT:1>N <DXBQSL_SENT:1>2 <COMMENT:10>ARRL DX CW ><DXBPFX:2>HB <DXCC:3>287 <DXBMGRN:1>1 <DXBAWD:1>0 <DXBSEL:1>0 <DXBVAL:1>3 ><EOR> > >That created the result in LoTW of a second unconfirmed QSO: > >Details K1EP WA1ABC 2005-02-20 >19:29:39 20M CW 14.094 SWITZERLAND >Details K1EP WA1ABC 2005-02-20 >19:29:00 20M CW 14.09400 > >It did not fix the problem, so the QSL from LoTW still has the one >with the seconds, so when I do a report, I still get the time with seconds. > ><APP_LoTW_OWNCALL:4>K1EP ><STATION_CALLSIGN:4>K1EP ><CALL:6>WA1ABC ><BAND:3>20M ><MODE:2>CW ><QSO_DATE:8>20050220 ><TIME_ON:6>192939 ><QSL_RCVD:1>Y ><QSLRDATE:8>20090325 ><eor> > >About the only thing I can think of right now to fix this problem, is >to write a script to edit the downloaded LoTW report and change any >seconds to :00. > >Any other thoughts?? > >______________________________________________________________ >Dxbase mailing list >Home: http://mailman.qth.net/mailman/listinfo/dxbase >Help: http://mailman.qth.net/mmfaq.htm >Post: mailto:[email protected] > >This list hosted by: http://www.qsl.net >Please help support this email list: http://www.qsl.net/donate.html ______________________________________________________________ Dxbase mailing list Home: http://mailman.qth.net/mailman/listinfo/dxbase Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
