Log4OM

I have around 3700 logs in the database (just over 50% of its capacity) and 50 of these logs need to be edited as I forgot to add an essential piece of information.

I tried opening each one of them individually however every time I open a log it takes about 30 seconds. This is not practical.

My questions are. Does anyone have any idea of why opening a single log takes so long ? My computer is fine and fast for any other application. It just hangs on LOG4OM.

Also, is there any other way to open the LOG4OM database in another application, edit what I need to edit, then save it back ?

Thanks.

Assuming your using the standard database in Log4OM it's capacity is over 130000 QSO'S

Check out bulk update in the user guide which makes it possible to edit hundreds of QSO'S in one pass using the QSO manager

Thanks for that. I will take a look at this.
The interface says Maximum 7000 logs.....I am with 3700. Not sure where you got 130,000 logs. Yes, I am using the standard database of LOG4OM version 2.17

zl1mto wrote: ↑02 Oct 2021, 22:15 Thanks for that. I will take a look at this.
The interface says Maximum 7000 logs.....I am with 3700. Not sure where you got 130,000 logs. Yes, I am using the standard database of LOG4OM version 2.17

You are getting confused with the maximum number of QSO's being displayed and the total capacity of the database.

You can change the displayed number temporarily on any grid or permanently in the program config.

Are you not confused between logs and QSO ?

zl1mto wrote: ↑02 Oct 2021, 21:19 I tried opening each one of them individually however every time I open a log it takes about 30 seconds. This is not practical.

I have this same problem opening QSOs individually. I also see this same lag in other areas of Log4OM. I've tried everything that has been suggested in past threads (performance tab settings, new database, reinstall - I even bought a better GPU to see if that would help). My system is a fairly new i5, 16GB RAM, SSD. I've been working around the issue for some time now.

The issue is somewhat relieved when the telnet cluster is off. I've also tried filtering spots directly on the cluster node to reduce the number of spots that Log4OM has to process. That has helped some.