Log4OM

PA0FVH

Version 2.14.00 cured the problem. All DB refreshes are much faster now. This is a significant improvement for users of MySQL.

Thank you Log4OM team.

Fred

PA0FVH

I am on MySQL (MariaDB v10.5) and I am experiencing the same issue. If I switch to QSLite the refreshes are fast.

73 Fred

PA0FVH

The issue with the default QSL sent value (Requested) is fixed in Log4OM version 2.8.0.0.
TU Daniele and the team.

73 Fred

PA0FVH

Hi all, I am running v2.7.0.0 and JTalert 2.16.7 and QSO's added by the UDP connection are getting QSL sent = No value. My default QSL sent status = Requested. Manual QSO input in Log4OM sets the correct QSL sent = Requested value. I never had this issue before, so I guess it's related to v2.7.0.0 7...

PA0FVH

Fixed in version 2.2.0.0

TU Fred

PA0FVH

Log4OM_QSL.jpg Mike, I have a similar issue, but explainable. My pre digital era DXCC award is linked to my LoTW account at the LoTW website. These awarded QSLs are stored as DXCC country, mode and date. No callsign and no band information. Parsing the information in the QSL section of the ADIF fil...

PA0FVH

Version 1.31.1 cured the DB issues, loading and QSO editing.
Thanks for the quick response.

73 Fred

PA0FVH

Besides the long loading time of the database editing an existing QSO record takes forever to save.
Also the WAS state fix doesn't seem to work.
Because of the increased editing time I went back to the previous version and got the speedy performance back.

73 Fred

Search found 8 matches

Re: A way long Refreshing on V2.13

Re: A way long Refreshing on V2.13

Re: QSL sent = No from JTAlert

QSL sent = No from JTAlert

Re: LoTW download - QSO dates in 1945????

Re: LoTW download - QSO dates in 1945????

Re: Log4om 1.31.0.0 database issue

Re: Log4om 1.31.0.0 database issue