Log4OM

Good evening OMs,
a friend of mine installed Log4OM V2 a few days ago and everything went well until, from July 10th, something never seen before happened: selected a spot from the cluster and made the QSO, after clicking on the (+) the same is not saved in the Recent QSOs (logbook).
I tried them all:
- moved the sqlite file to another folder (including desktop)
- did a rewrite reinstalling log4om
- I created a new sqlite file
- I checked the permissions of the file (read and write)
nothing... it doesn't save QSO anymore.
Log4OM version is the latest.
Thanks in advance for your support.
Max

Max,
Firewall or antivirus blocking possibly?

UAC set too high?

Have you tried running Log4OM as an administrator?

Can you save using the enter/return key on keyboard instead of +Plus sign?

Thanks Terry,
yes, I confirm. I always start Log4OM as administrator (even my friend) and I tried disabling the antivirus. Nothing. Still not logging QSOs.
We also tried importing an ADIF from JTDX and that didn't work either. It appears that it fails to overwrite the sqlite file.

just a news ... if I copy the sqlite file on onedrive it works. Why? I do not understand!

IK0TIX wrote: 14 Jul 2023, 21:54 just a news ... if I copy the sqlite file on onedrive it works. Why? I do not understand!

Try this.......

Export an ADIF of the log

Create a new SQLite database

Import the ADIF file to the new database

Dont delete the original database until your sure all is good

Hi Terry and thanks again for the support.
I checked my friend's PC settings and found out that any folder I create is no rewritable restricted.
In short, I think it's an administrator permissions (Windows 11) issue. What's more, over the past few days, Windows has had a major update...
I'm afraid that a deeper check on these admin settings will prove the real cause of the problem. For the moment we have saved the SQLITE file on OneDrive but the problem on the PC will have to be solved. I think my friend will have problems with other files (e.g. MS Office).
Thanks again, I think this ticket can close in this way: Log4OM no guilty.

73
Max

OK Max, thanks for the update.

I suspect your correct as I have seen this on two other occassions and all related to a Windows update.

Keep in touch and thanks again for your support of Log4OM

I would not recommend you use OneDrive for the Log4OM database.

Google Drive is much more robust. As much as I like OneDrive it does not work well for this database.