Error reading from Callbook databases

[EI4KF]

Hello Erik,

I don't think the JTDX sequence has nothing to do on this. Swisslog retrieves info as soon as a callsign is in the DX Call field from JTDX regardless the sequence. What is important to me to know is if the operator name is OK in the QSO Entry window when the QSO is started but is changed when logged. Excuse me if you told me this before but this matter it's not clear to me yet.

VERY IMPORTANT: The operator field of JTDX prevails over the info set in Swisslog! so if Swisslog retrieves the info well but you have a different name in the Log QSO window, this name will be saved in Swisslog. Review carefully this because it could be the reason of this issue. If you have a wrong name saved in the JTDX Logbook, this will always be set in the Log QSO window. I suggest you to export your logbook into JTDX by using the Tools / Export log to WSJT-X to ensure your JTDX logbook contains the same info as the Swisslog logbook.

Best 73

Hello Jordi

JTDX log book was created from Swisslog. It is identical. This is not the reason for the issue. I did say before but I understand how things get lost in a long discussion: I see the correct Operator Name in QSO Entry but for these QSOs it is not saved to the Operator Field in the log. The JTDX sequence is irrelevant, I was answering about timings but misunderstood your question. Essentially: the data is retrieved from qrz.com and is displayed correctly in Entry QSOs. If the QSO save is only a short time since the last save, the correct Operator Name does not go to the logbook which somehow fills the Field with data from the previous QSO. This continues unabated until there is a longer delay between QSOs or I stop and restart Swisslog.

How to fix it is another matter!! At least when this happens now, as it did today again, updating affected QSOs from online databases now works so I can put it right. 

Erik.