Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Coming back to Swisslog importing ADIF data from DXKeeper
07-01-2017, 09:59 AM,
#1
Coming back to Swisslog importing ADIF data from DXKeeper
Dear All
I have been using Swisslog since the early DOS days in the eighties being one of Walters first customers. In January 2014 I started to use JT9 and JT65 as my main modes of operation. This made me switch to the DXLabs suite as my logging software. I kept Swisslog running and did not export my SWL database to DXKeeper. I did several DX-peditions in the past using the DOS and Windows versions of Swisslog and still receive many paper QSL’s (going back 15 years and more!). Swisslog allows me to handle these QSL’s really well, much nicer than DXKeeper.

I was very happy to see that version 5.94 supports WSJT-X, ClubLog, and DXLabs Commander. This is a great effort from Jordi. A great THANK YOU for that Jordi!! It is also great to see that the country table is being kept up-to-date by Eric, great job guys! This should allow me to do most of what I currently do with DXLabs. For me only automated eQSL handling is missing. I am therefore preparing my move back to SWL.

Here are two questions that I need support with:

I did an ADIF export from DXKeeper and then used the field assignment dialog in SWL to import the log from DXKeeper. Some of the DXKeeper specific fields do not exist in SWL. I do not need most of them. However, some of the existing SWL fields cannot be selected to be assigned to the import fields. These fields are related to ClubLog, LotW and eQSL. My understanding is that ClubLog, LotW and eQSL status cannot be imported (is this assumption correct?) and that ClubLog and LotW synchronisation have to be done using Swisslog. For ClubLog this is no problem. I will just delete the current ClubLog database and create a new one. For LotW I am not so sure. My LotW was already synchronised using DXKeeper (the DXKeeper database is only from 2014 until today, the SWL database from 1981 to 2014). I assume I can just do another LotW synchronisation with all LotW fields in the imported records empty and the LotW software at ARRL will take care of my data. I just need to follow the sequence defined by SWL. Is my assumption correct?

I imported the ADIF file into a new database created for testing. The import dialog runs through OK without any error messages. However, when I want to look at the imported log file using the All fields logbook (slow).SPQ view I get the following error messages:

Parameter QSO.L_CLUBLOG_QSO_UPLOAD_STATUS has no default value
and
TabQuery: operation bei geschlossener Datenmenge nicht ausführbar

This does not happen with other views (since they do not use that field). It also does not happen when I import the ADIF file into my existing SWL HB9CQK database 1981 to 2014 (do not worry, I have many backups, so I can play around with my real database without the risk of losing anything).
I appreciate if anybody can tell me that my assumptions above are correct or not and how I can solve the error message issue. By the way: I just did a clean new administrator install of version 5.94 avoiding the Windows issues. I just had to copy my database and reports and was done.

Thank you very much for your support and good DX, Frédéric, HB9CQK
Reply


Messages In This Thread
Coming back to Swisslog importing ADIF data from DXKeeper - by HB9CQK - 07-01-2017, 09:59 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)