Log4OM

I had upgraded, and all was good until I needed to import ( any ) adi file. it will not allow me to do it. it will let me browse and select the file, but thats as far as it goes. i downrgraded to 2.17, and the import works fine, same files

is there something different on 2.18

no I do not run as elevated, and the programs are not even in the program files folders

for now I use 2.17.0.0 with omnirig for cat ( hamlib failed again )

So where did you install log4om and where is your database sqlite file stored

What O/S

log4om is installed on d drive, the sqlite file is on google drive, and this is working with 2.17.0.0 verified, because I reinstalled and tested same adi file, and it imports fine, as it did before.

has something changed in 2/18?

btw, I have no issue with logging from wsjtx, via jtalert into log4om ( either version)

sorry forgot to add now been using windows 11 for about 3? weeks?

Does it make any difference how many QSO'S are in the ADIF file

When using an install to other drives it's best to use the portable version if you can.

There have been some strange permission issues with Win 11 not just related to Log4om

just an update, after reverting to v2.17.0 and having success, i tried again, using same adi file ( lastqso.adi) from jtalert . it worked fine in 2.17, but in 2.18, I can browse to it, select it, but when I tap on import, absolutely nothing happens...

I will try the portable version, and see if it is ok on my d drive..

after that I may try to put it back on c: drive, and test..

ok, I have reinstalled v2.17, working ok in default porgram files location, on c drive. then install 2.18.0 import is not continuing as before..

hopefully I will have no contestes to load later. but I will try with more than one entry to see if that changes anything

update, it seems the adif import , using a single update will not work for me, but if I copy and paste the same data, but change callsigns only, save then the import works.. whats different

I copied <CALL> TO <EOR> . I could send the adi file if you want

ve3wej wrote: ↑07 Dec 2021, 14:04 update, it seems the adif import , using a single update will not work for me, but if I copy and paste the same data, but change callsigns only, save then the import works.. whats different

I copied <CALL> TO <EOR> . I could send the adi file if you want

Dave,

Some issues have been noted and discussed on the thread (linked below) regarding ADIF imports of "one" QSO as related to the release of V2.18.0.0

https://forum.log4om.com/viewtopic.php? ... 8&start=10

ok, I will endure, but waiting for the fix on next version update