LogBook/Import: importing .adi files generates 'DXCC missing' errors

[K6OK]

What happened? How can it be reproduced? Provide as much information as possible.

I used another program for a contest, then used it to make an .adi file. When importing that .adi file into QLog, it says DXCC is missing. QLog successfully adds the QSOs to my log but

-- DXCC field is blank
-- Country field is blank
-- LOTWs field is set to 'N'

In QLog I see no convenient way to edit these fields for hundreds of records. I would like to suggest either:

Upon import, QLog queries cty.dat with the callsign and automatically fills in the DXCC and Country fields. Also automatically set the LOTWs field to 'Q' (same as what QLog does when connected to WSJT-X)
-- or --
Give the user a global edit option when used with a Filter. Such as "For all records shown, update DXCC and Country from cty.dat?" and "For all records shown, add to LOTW queue?"

Thank you for all your work to make QLog a very good program. -- 73 Jim K6OK

QLog Version

0.49.1

Which OS are you using?

Linux

QLog Installation Method

Flatpak

Installation Details

No response

[aa5sh]

When you import there is an option to 'Update DXCC Entity Information' at the bottom:

May be worth just selected those QSOs and deleting them and reimporting.

[K6OK]

I missed that option, thank you. I just made a couple of quick QSOs and did a manual import. That worked well, QLog filled in the missing DXCC and Country fields.

But... the LOTWs field is set to 'N.' I had to manually edit the field to 'Q' to enable uploading to LOTW. I can live with that, it's easy to select all of the 'N' rows and change them all at once to 'Q.' It would be nice to have an option on the manual import form that says |_| Queue all QSOs for LoTW uploading. Tnx for your quick response.

[aa5sh]

For LoTW if you look in the upload window there is an option to include QSOs with 'No' status. Look right below my callsign - in the filter section. Give that a shot and you may not need to edit them.

[foldynl]

@aa5sh I’m not sure, but it happens quite often. I think we should probably change the default to checked so that QLog recalculates DXCC automatically. What do you think?

[aa5sh]

I wouldn’t want it to recalculate automatically for the entire input maybe have a check if the DXCC is missing on a contact have it add it? I’m not a big fan of overwriting data just because so I like have have the checkbox. But can append missing information.

…

On Mar 31, 2026, at 2:06 AM, Ladislav ***@***.***> wrote: foldynl left a comment (foldynl/QLog#983) <#983 (comment)> @aa5sh <https://github.com/aa5sh> I’m not sure, but it happens quite often. I think we should probably change the default to checked so that QLog recalculates DXCC automatically. What do you think? — Reply to this email directly, view it on GitHub <#983?email_source=notifications&email_token=AUEEMXQAOQYR72WKI6SRYA34TNU55A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJWGA2DCMJQHE32M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4160411097>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXWXNO6FB2ZNS4EQ46D4TNU55AVCNFSM6AAAAACXFRFSAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNRQGQYTCMBZG4>. You are receiving this because you were mentioned.

[K6OK]

Yes, I also think the default should be automatic DXCC and Country populate but only when that data is missing. QLog does that now if I have WSJT connected in real time. I think importing .adi files should have the same behavior.

[foldynl]

@aa5sh I looked into the code. During import, if DXCC information is missing, warnings are generated indicating that the information is absent. No automatic updates are performed now. It is strictly dependent on that DXCC Update toggle. If it is disabled, nothing happens with DXCC, but warnings are generated. When it is enabled, everything is updated.

a check if the DXCC is missing on a contact have it add it?

I don’t think it should update only the missing data, because that would make the checkbox confusing for the user in terms of what it actually does. On the other hand, users probably don’t read warnings, since this issue keeps recurring quite often.

Another option would be to report an error instead of warnings. That might motivate users to actually notice it.

[aa5sh]

Yeah making the error’s may make it more noticeable. No easy decision with this. But that may be the best first step and see how it goes.

…

On Mar 31, 2026, at 1:12 PM, Ladislav ***@***.***> wrote: foldynl left a comment (foldynl/QLog#983) <#983 (comment)> @aa5sh <https://github.com/aa5sh> I looked into the code. During import, if DXCC information is missing, warnings are generated indicating that the information is absent. No automatic updates are performed now. It is strictly dependent on that DXCC Update toggle. If it is disabled, nothing happens with DXCC, but warnings are generated. When it is enabled, everything is updated. a check if the DXCC is missing on a contact have it add it? I don’t think it should update only the missing data, because that would make the checkbox confusing for the user in terms of what it actually does. On the other hand, users probably don’t read warnings, since this issue keeps recurring quite often. Another option would be to report an error instead of warnings. That might motivate users to actually notice it. — Reply to this email directly, view it on GitHub <#983?email_source=notifications&email_token=AUEEMXQ6KJG7O7JREAY2W7D4TQDA5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJWGQ2DQOBSGIZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4164488223>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXWPOLJCCR5UIXMFUIL4TQDA5AVCNFSM6AAAAACXFRFSAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNRUGQ4DQMRSGM>. You are receiving this because you were mentioned.

[Sattelite]

@aa5sh @foldynl TNX ! This worked for me and imported nearly all 30K + qso again and now every QSO showing the country flag :-) Great program ! and I use the qlog.db on a NAS and from every PC with Qlog installed, I can access the
Log by using a symlink. Works great :-) TNX for all your work :-)

[foldynl]

@Sattelite

and I use the qlog.db on a NAS and from every PC with Qlog installed, I can access the Log by using a symlink.

Honestly, I’m not very enthusiastic about this. I understand that nowadays users often have multiple computers and are “spoiled” by cloud services. Unfortunately, Qlog was not designed for this.

Modifying things so that the file is stored on a NAS can have unexpected side effects that I cannot fully anticipate right now. A lot depends on the implementation of the protocol used to expose the file from the NAS. Various issues can occur, ranging from incorrectly implemented file locking to situations where you might lose data, because a local system handles data differently than a remote file system. Unfortunately, many users are not able to foresee these problems.

Another potential issue is that SQLite operates in WAL mode, meaning changes are first written to a separate file and only later committed to the main database file. You can probably imagine what might happen if there is a problem with the NAS and you lose the data at the moment those changes are being merged into the main file.

A database file is not just a simple file that is always consistent under all circumstances, which is why I’m not very comfortable hearing that users manipulate it outside of how Qlog is designed to handle it.

if it works for you, there may not be much I can do about it… unless I start checking whether the DB file is really a file and not a symlink. ;-)

[Sattelite]

@foldynl TNX for the warning ! Yes, I am aware of the faults that happen when Qlog is opened simultaniously on another computer. Therefore I always close Qlog by using a script when going into suspend. Besides the NAS is on a Rasp Pi and
every night a backup is made automatically in case something goes wrong. But Qlog is the best solution I've found among
all other logprogs and this works for me. TNX again :-)

[foldynl]

@Sattelite Unfortunately, it’s not just about preventing two instances from accessing the same database, but also about the case where only a single instance is communicating with the DB file and network filesystem. You can use Google and search for “SQLite Samba issue”, or read a bit about WAL mode, and you’ll see that my concerns are justified.

[Sattelite]

@Sattelite Unfortunately, it’s not just about preventing two instances from accessing the same database, but also about the case where only a single instance is communicating with the DB file and network filesystem. You can use Google and search for “SQLite Samba issue”, or read a bit about WAL mode, and you’ll see that my concerns are justified.

You're right foldynl ! TNX for pointing to this aspect !