Import QSOs

[om3by]

Hi
I am a new user of Qlog. When importing QSOs, I was unable to import all QSOs.

Can anyone help with this problem?
TNX Vlado OM3BY

[aa5sh]

It's hard to tell from this but if you want to send me your ADIF I can take a look and see if I can help you determine what can be causing this.

73

Michael, AA5SH

[om3by]

Hi Michael
Thank you for your willingness to help me. I am sending you the ADI file. It is from LogHX, which I still use. Rename OM3BY.txt to OM3BY.adi.
Thank you very much.
Vlado OM3BY
OM3BY.txt

[aa5sh]

Ok I just tried your file in a test database. I had 4 errors due to DXCC issues - like 403a instead of 4o3a and D1M which didn't have DXCC info.

Here is test station setup:

Then in Import Dialog I had like this. By having the 'My Profile' set it will add missing information like Station Callsign, MyDXCC etc from the station profile you select.

You do have 47 duplicate QSOs so I answered 'No to All' here:

So it wound up importing 25,4007 records.

I'm thinking you have a corrupt/bad database file. If you have logged any new QSOs in QLog I would recommend exporting them to an ADIF file and backup then rename the 'hamradio' folder where your database is stored to save a copy. Then resetup QLog and re-import your QSOs. Not sure if you chose the opton to delete all qsos in the settings. But if I did that and tried to reimport I got the same foreign key errors. @foldynl correct if you think it may be something else going on here. Your database file is located in one of the following locations depending on OS:
QLog Database is located:

Linux - $HOME/.local/share/hamradio/QLog
Linux - flatpak - $HOME/.var/app/io.github.foldynl.QLog/data/hamradio/QLog
Windows - C:/Users//AppData/Local/hamradio/QLog
MacOS - $HOME/library/Application support/hamradio/qlog

[foldynl]

@aa5sh the analysis was done perfectly. I also cannot see any reason why something like this should happen under normal circumstances.

@om3by Follow exactly what @aa5sh recommended: remove the current QLog database (or QLog folder) and create it again from scratch. Please note that the function in the Setting -> Danger Zone will not help in this case. The database file must be deleted manually.

[aa5sh]

I was looking more at your ADIF file and I think I found the true problem. Not sure why it would import sometimes for me but fail at times. But in your ADI there are some data inconsistencies that is causing the error. Most notably with QSL_SENT_VIA. It is an adit enumerated value that only allows B, D, E, or M. But you have lots of Ignore, OQRS, Igmore, mail, mailQSL, G, and similar values in there. These are causing the foreign key errors. I'm gonna submit a proposed changed to change any invalid values to NULL. I imported this in this fix and then exported so the values should be clean now if you want to see if this will import better.
OM3BY-Clean.txt

[foldynl]

Honestly, I haven’t tested it because I’m currently working on too many things at once, and it is starting to show in the quality of my work. :-(

@aa5sh: But you are right. There is a problem with values that are not defined in ADIF. I also saw your PR. In general, I agree with this. However, I also think it should be improved so that errors of this type are shown to the user. I need to analyse how to present them to the user in a reasonable way and, more importantly, how to integrate this into the overall architecture.

[om3by]

Hi Michael Ahoj Ladislav
Thank you very much for your help. I would not have been able to identify this error. I made this error myself when I wanted to have more accurate information in the QSL_SENT_VIA field. LogHX allowed me to overwrite this field. I imported your edited file without errors. So far I am getting to know Qlog and I like it. You are doing a great job. I am not a programmer, but maybe the time will come when I will be able to contribute to this project. By sharing experiences, suggestions.....

Vlado OM3BY