Strange log link
Posted: 22 May 2021, 06:54
Hi all
After the latest update I made of JTAlert (now using v2.50.1), some strange thing happen.
Using L4OM version 2.13.0.0, on Win 10.
One callsign (F6EXV) workes perfectly between JTAlert, JTDX and L4OM.
Now, on my other callsign (F4KMA), QSOs from JTAlert are logged into JTDX log OK, but they are not logged to L4OM.
I have checked that the L4OM logging is enabled, send dx call to L4OM is enabled, and there is a correct port number for the adif message port.
BUT QSOs are not logged to L4OM.
When i check the connection to the log (.../F4KMA.SQLite), the link is correct, but the database shows a last QSO which is not correct (several days ago) and the QSO count is wrong.
How can JTAlert point to the right link, and have a wrong database connected ?
A side question : when doing a backup, is the SQLite database saved as such, or just an adif file and a config file ?
I am puzzled !
After the latest update I made of JTAlert (now using v2.50.1), some strange thing happen.
Using L4OM version 2.13.0.0, on Win 10.
One callsign (F6EXV) workes perfectly between JTAlert, JTDX and L4OM.
Now, on my other callsign (F4KMA), QSOs from JTAlert are logged into JTDX log OK, but they are not logged to L4OM.
I have checked that the L4OM logging is enabled, send dx call to L4OM is enabled, and there is a correct port number for the adif message port.
BUT QSOs are not logged to L4OM.
When i check the connection to the log (.../F4KMA.SQLite), the link is correct, but the database shows a last QSO which is not correct (several days ago) and the QSO count is wrong.
How can JTAlert point to the right link, and have a wrong database connected ?
A side question : when doing a backup, is the SQLite database saved as such, or just an adif file and a config file ?
I am puzzled !