Log4OM

My venerable PC has finally died.... I do have access to the drives and (fortunately) had a laptop to set up everything on. Reinstalled current version of Log4OM and copied over the SQLLite database. Log4OM recognized that database and I can access it....but I can't write to it! It complains that it is a read only database.

Any input on how to enable this as the default database and have it be writeable?

(I'm a 30 year veteran of systems admin so feel free to be technical. I'm not scared.... )

73's

some progress. I found all the user specific config information and restored that. So my old profile and all login information was preserved (from c:\user\<me>\appdata\roaming\log4om). That restored just fine and everything was happy. Except the system still thinks the database is read only so no writing log entries...

Aha! Figured it out! So....boys and girls, if you have the database within the Log4OM program directory (as did I) and you have updated to Windows 10 (other versions might be affected but this is my case)....there is no write authority to that directory. Probably a enhanced security thing. Copying the database to a writeable area (like documents) fixes the issue and it is all good (and remembering to open it as the new database)

KD5RXP wrote:Aha! Figured it out! So....boys and girls, if you have the database within the Log4OM program directory (as did I) and you have updated to Windows 10 (other versions might be affected but this is my case)....there is no write authority to that directory. Probably a enhanced security thing. Copying the database to a writeable area (like documents) fixes the issue and it is all good (and remembering to open it as the new database)

That would do it!

I've added a new function to prevent users from saving the database in the same folder where Log4OM application resides, some releases ago...
but it works only when you try to create a new database....
Old users with database in this path aren't advised by anything...

Good spot
lele
IW3HMH