Log4OM

Mika,
Dont worry I think its a local machine issue and we are checking a fix now.

The issue is
SQLite standard date format is yyyy-MM-dd HH:mm:ssZ and even if we are forcing that format, your PC is saving time as HH.mm.ssZ using dots as separators instead of ":" so when loaded the format is not recognized.

We have prepared a workaround, that will possibly work without doing more complex and time consuming activities when parsing data.

It is being tested by another user with the same issue, but if you would like to email me I will provide a modified download for you to test also.

Thank you Terry!

That's probably reason for this behavior.
Please send me modified download version for testing.

73 de Mika OH4NVX

oh4nvx wrote: 17 Jan 2020, 12:43 Thank you Terry!

That's probably reason for this behavior.
Please send me modified download version for testing.

My email is oh4nvx[at]gmail[dot]com

73 de Mika OH4NVX

Just sent link to a download from my dropbox

I'll let you know how it works in the evening!

TNX es 73 de Mika OH4NVX

Just tested Imported ADIF from HRD, same problem also with manually entry
qso totally blank, tried to change Windows Setting Date & Time,Region format
to default same result.
Tnx es 73
Anton - YB5QZ

YB5QZ wrote: 17 Jan 2020, 13:42 Just tested Imported ADIF from HRD, same problem also with manually entry
qso totally blank, tried to change Windows Setting Date & Time,Region format
to default same result.
Tnx es 73
Anton - YB5QZ

Email me and I will send you download of trial maintainence release if you want to test it

Thanks Terry, my email is [email protected]
73,
Anton -YB5QZ

YB5QZ wrote: 17 Jan 2020, 06:43 I've installed v2 and QSO entered manually few qsos and Adif imported
some qsos as well but wonder that Recent QSO (F8) window doesn't appear qso list (blank)
even though on the bottom left has appeared Number of QSO 68.
running here with win10 64b.
What I am missing ?
Any help much appreciated.
Tnx es 73
Anton - YB5QZ

I had the same problem using Norwegian language Windows 10.

Changing to UK language and punctuation settings in Windows, using "intl.cpl" from Command line, did initially NOT solve the problem.

BUT, creating a new SQLlite database in Log4OM using UK Windows 10 settings solved the problem, also when later changing back to Norwegian Windows settings.

73 de LB2EG Richard

Terry, trial maintenance release solved the problem.
Now logged QSO's are visible!

TNX!
73 de Mika OH4NVX