ADIF Functions - Monitor

[G6FZU]

Has the "Upload QSO to External Services" check box been disabled so the bug with that state machine doesn't have to be fixed. I'm guessing this is a mechanism for forcing us to use the UDP mechanism. The problem for me is that I've never used the UDP option so have no idea what to do with JTDX in order to get that half working.
This was all working in the last release I have been using for 12 months and I'm now, like others, regretting upgrading.
A popup stating this has been removed when you select that option would have saved me a week debugging my settings and saved me the £85 to Ham Radio Deluxe (which I don't like).
Can I use SQLite editor to activate it in the database?

[G4POP]

So how are you sending the QSO's from JTDX to Log4OM if your not using UDP?

What exact version number of Lg4OM are you using (See help/about)

[G6FZU]

My apologies, I'm not being very clear. Log4OM reads the JTDX ADIF file in a few seconds (<5s), what doesn't work is the flag to indicate you want to upload the new QSO to online logbooks after its been read. Setting that flag does not persist beyond "save and apply". Go back into program settings and that flag has cleared again... and again...
If I manually enter a QSO I'm bypassing the ADIF Monitor function so that gets uploaded to QRZ et al.
Because I'm using TSQL to upload to LOTW that works perfectly too.

In summary, no QSO copied from JTDX using ADIF Monitor gets uploaded to the online logbooks: QRZ, Hamlog, etc.

I was told by another user that UDP works but my problems are twofold:
1. I've never used that mode and its just another mechanism for me to screw up.
2. I love the ADIF monitor because running Log4OM means it will catch up with the QSOs. I'm afraid that when I forget to run Log4OM with JTDX I'll lose real time QSOs.

[G4POP]

My apologies, I'm not being very clear. Log4OM reads the JTDX ADIF file in a few seconds (<5s), what doesn't work is the flag to indicate you want to upload the new QSO to online logbooks after its been read. Setting that flag does not persist beyond "save and apply". Go back into program settings and that flag has cleared again... and again...
If I manually enter a QSO I'm bypassing the ADIF Monitor function so that gets uploaded to QRZ et al.
Because I'm using TSQL to upload to LOTW that works perfectly too.

In summary, no QSO copied from JTDX using ADIF Monitor gets uploaded to the online logbooks: QRZ, Hamlog, etc.

I was told by another user that UDP works but my problems are twofold:
1. I've never used that mode and its just another mechanism for me to screw up.
2. I love the ADIF monitor because running Log4OM means it will catch up with the QSOs. I'm afraid that when I forget to run Log4OM with JTDX I'll lose real time QSOs.

Without you state a Log4OM version number I am not able to help you!

[G6FZU]

The very latest, labelled "hot fix".
I downloaded it 1 week ago.

[G4POP]

Please the actual release number - See Help/about

Yes I am 83 and the photo is about 8 years old

[G6FZU]

Version 2.30.1.0

[G4POP]

Version 2.30.1.0

OK I just checked using the same version on my Win 11 PC and the ADIF monitor settings in the config are persistent.

Its possible that a Windows update has changed the write permissions to that file or folder, please check that its not read only

Try a clean install (Uninstall Log4OM and do a fresh download and re-install) no settings will be lost unless you delete the user files so just use the windows uninstall function from the Add and remove programs dialog

[G6FZU]

Sorry, I forgot. I'm using Windows 10 if that helps.
I don't have any proble with ANY other checkbook, in that section or any other.
How would one checkbox be subject to the wrath of Microsoft?

[G4POP]

Sorry, I forgot. I'm using Windows 10 if that helps.
I don't have any proble with ANY other checkbook, in that section or any other.
How would one checkbox be subject to the wrath of Microsoft?

That is why I suggested a re-install!