[Dxbase] LOTW ADI Import to DXBase 2006 Error

Thu Apr 13 18:11:58 EDT 2006

Dave,

I think that what you are trying to do, is to "make" a
new database (from your LoTW download) - or ADD to
your existing database (from your LoTW download)??

Am I correct here Dave??

73 Joe wa6axe

Jack wrote:
> Dave,
> 
> Last time I looked into the process, the time that is returned by an 
> LoTW download is equal to the time of the QSO that is in your log.  In 
> other words, you upload your stuff, then you download.... the times 
> contained in the download are the same times based on what you 
> previously uploaded. Therefore, the process you are using is flawed 
> because your times don't match what is in your log.
> 
> Regards,
> Jack
> 
> ----- Original Message ----- From: "Dave Lee" <dlee at w6zl.com>
> To: <dxbase at mailman.qth.net>
> Sent: Thursday, April 13, 2006 11:35 AM
> Subject: [Dxbase] LOTW ADI Import to DXBase 2006 Error
> 
> 
>> DXbase Experts:
>>
>> I have the following ADIF file:
>>
>> ARRL Logbook of the World Status Report
>> Generated at 2006-04-13 06:00:30
>> for w6zl
>> Query:
>>   QSL ONLY: YES
>>  QSL SINCE: 2005-01-01 00:00:00
>>
>> <PROGRAMID:4>LoTW
>> <APP_LoTW_LASTQSL:19>2006-04-12 08:04:25
>>
>> <APP_LoTW_NUMREC:3>003
>>
>> <eoh>
>>
>> <APP_LoTW_OWNCALL:4>W6ZL
>> <STATION_CALLSIGN:4>W6ZL
>> <CALL:4>NL7G
>> <BAND:3>15M
>> <MODE:2>CW
>> <QSO_DATE:8>20031129
>> <TIME_ON:6>013033
>> <QSL_RCVD:1>Y
>> <QSLRDATE:8>20060412
>> <eor>
>>
>> <APP_LoTW_OWNCALL:4>W6ZL
>> <STATION_CALLSIGN:4>W6ZL
>> <CALL:4>NL7G
>> <BAND:3>10M
>> <MODE:2>CW
>> <QSO_DATE:8>20031129
>> <TIME_ON:6>004943
>> <QSL_RCVD:1>Y
>> <QSLRDATE:8>20060412
>> <eor>
>>
>> <APP_LoTW_OWNCALL:4>W6ZL
>> <STATION_CALLSIGN:4>W6ZL
>> <CALL:7>NP3D/W2
>> <BAND:3>40M
>> <MODE:4>RTTY
>> <QSO_DATE:8>20060402
>> <TIME_ON:6>030400
>> <QSL_RCVD:1>Y
>> <QSLRDATE:8>20060412
>> <eor>
>>
>> I use the NON-DXB import utility to import the file into an empty 
>> DXBase 2006 file.
>>
>> I then change all three QSO's to not confirmed.
>>
>> I then run the NON-DXB import utility again, again selecting LOTW ADIF 
>> as the import file type. (I would expect for all 3 QSO's to
>> be updated with LOTW as the confirmation method.)
>>
>> Only the QSO with NP3D/W2 gets updated. The other two QSO's error with:
>>
>> ERROR:  NL7G 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. NL7G 20031129 013000  15m  
>> CW 599 599 AK
>>
>> ERROR:  NL7G 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. NL7G 20031129 004900  10m  
>> CW 599 599 AK
>>
>> On the initial import, the seconds of time are set equal to 00 in the log
>>
>> Notice that the <TIME_ON:6> value of the NL7G QSO's is not 00, but the 
>> NP3D/W2 value does end in 00
>>
>> I ran this small test because I have a LOTW report file of over 800 
>> QSO's. Only the QSO's with the seconds equal to 00 will update my 
>> DXBase 2006 file. (over 400 errors)
>>
>> Dave / W6ZL
>>
>>
>>
>> ______________________________________________________________
>> 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
> 
> 