Log4OM

Hello,
I think I found a very nasty bug in Log4OM ver. 2.21.1.0:

When editing QSOs from the QSO Manager card, the date and time of the QSO automatically changes to the current one. When you go to editing from Recent QSO's (F7) this error is not present.

Tom, SQ2TOM

I cannot replicate this please provide more information

When I double-click on the QSO in the QSO Manager tab, the QSO Edit tab opens with the changed date and time (QSO Start) as it is at the moment, and not the actual time of making the connection, e.g. last year.

SQ2TOM wrote: 11 Apr 2022, 09:18 When I double-click on the QSO in the QSO Manager tab, the QSO Edit tab opens with the changed date and time (QSO Start) as it is at the moment, and not the actual time of making the connection, e.g. last year.

That is exactly what I tried and date/time was unchanged

What is windows language and keyboard setting?

Have you tried English?

I noticed that the QSOs that I edited earlier in ver 2.21.1.0 open for editing with the date of the QSO, but the QSOs saved earlier in ver 2.20 and not edited open for editing with today's date.

On the other computer I have version 2.20 and it's OK so it's not an issue windows language and keyboard setting

Terry, I am so sorry that my English is so poor

When I said have you tried English I was referring to windows 10 language and keyboard settings not critising you language which is excellent

just in case my English is not so good, the picture will show better
double click

changed keyboard settings to english - no improvement.
But I noticed that this problem only affects the older QSOs that were logged in Ham Radio Deluxe ver 5.24 and imported from the ADIF file to Log4OM. Maybe the problem is that in HRD there was a different entry for QSO start and QSO end ....

SQ2TOM wrote: 11 Apr 2022, 20:19 changed keyboard settings to english - no improvement.
But I noticed that this problem only affects the older QSOs that were logged in Ham Radio Deluxe ver 5.24 and imported from the ADIF file to Log4OM. Maybe the problem is that in HRD there was a different entry for QSO start and QSO end ....

More likely that HRD used a different time format from that required

I downgraded the version to 2.20.0.0 and the problem is gone