All, Not so hoaky. This morning I did exactly what Courtney suggested and it works fine. I was dealing with a LoTW download of 2816 "QSLs" which was my current tally as of last night. Just for added info by letting DXBase 2004 "process" this "log":
2816 QSO records 32 DXCC mixed total .. including XT2DP qso. The DX participation grows daily. 47 States "confirmed" .. The RTTY guys are leading the pack. A couple observations on the process with implications to Jack's future spec on his LoTW processing: 1. The present import process set the CFM field to "Card". It had no idea that these were LoTW confirmations so I imagine the default is "Card" 2. QSLRDATE was set correctly as the LoTW confirmation date 3. Warnings were issued for all the VE "Province" entries as not being "States". The QSO was imported correctly without forcing the province into the "State" field of the log. 4. The states were imported properly. 5. Grid entries were made properly. But the data is optional by the originator and the format also varied as both 4 and 6 character sets were seen. eg: FN42 and FN42NN 6. I saw no time discrepancies in any of the records I manually examined. I have not tested this by importing this ADIF file directly into my master log of something like 63000 Qs. I will do this as a test log but I really have no way of digesting the error log that would result from all the "dupes". And I may not find actual added Qs that are time discrepancies because the import process will not give me a list of the additions. But I will give it a shot. For the near term, I would like to be able to use a manual process to import that ADIF file as a "special" import to my existing log database. Functionally it should simply populate my "existing" log record by matching the callsign, date, and time with a simple update of the CFM field with "LoTW". No other field need update is needed right now but could be a future consideration. I am assuming I can do any award tracking and other reporting from that simple confimation tag. Update of other fields including QSLRDATE and the other "data" could be considered at a future release. In my simple thinking, an added selection to the Non-DXB Import program "Source Data Type" as something like ADIF-LoTW would allow me to trigger such a "special" import process. We cannot cannot process actual award "credit" yet but just being able to "automagically" update the LoTW QSL "received" record will go a long way toward being ready to prepare a DXCC or WAS submission. As Jack mentioned earlier, the ink is still wet on some of the processes at the ARRL but DXBase 2004 has set us up to deal with the new process quite nicely. My 0.02 worth, 73, George .. W1ZT At 08:16 PM 10/13/2003, Jack wrote: >Hmmmmm, this may seem hoaky, but Bill loves this stuff: > >How about this: > >1. Set up a new empty database in DXbase. >2. Perform an ADIF import of your LOTW file into this newly created >database from 1 above. >3. Use the User Designed List report options to create a report that >includes all the fields. >4. Export the report to Excel > >Now I don't know if this would work, but who knows...... Just don't ask me >to support it... hihi... > >Courtney > >----- Original Message ----- >From: "FireBrick" <[EMAIL PROTECTED]> >To: "DXBase List" <[email protected]> >Sent: Monday, October 13, 2003 2:26 PM >Subject: [DXBase] anybody ever see a > > > > Anybody ever see a program to port .adi to comma delimited? > > > > If I could do that, than I could read the qslreport in Excel or Access. > > > > Or is that a wrong approach? > > > > What I was thinking was, port to Excel or Access and sort by >callsign/date.
