Band and RX Band Empty on Edit

[G0BON]

V2.28.0.0
When I go to edit a QSO the band and Rx Band fields are empty, did not have this problem in v2.27

LOG4OM EDIT.JPG (42.01 KiB) Viewed 1032 times

[KI5IO]

Ivan,

Have you restarted Log4OM to try and reset?

I've tried every way I can and am not able to replicate your situation.

When you made/saved the QSO was all the information on the Main UI at that time?

Is that relevant information visible in your Recent QSO's (F7) panel?

Image of one of the many Edit QSO screens I tried this afternoon as well as my Recent QSO's panel.

.

[G0BON]

This is really strange indeed.
What I have deduced further is that the empty fields are on QSO that I imported from an ADIF.
If I go into EDIT QSO and change the band and RX band to 40mtr. I save and exit and then go back into edit QSO and it only shows the RX band field filled in.

Any new Manual QSO entries and the fields are OK, No problems

Attached is a txt file rename .txt to .adi
The QSO on the 04/06/23 is a manual input the entry on 08/06/23 is from an ADI entry.
I dont know whether you can replicate it fro this?

[KI5IO]

Ivan,

And you are importing the ADIF from what application that created the ADIF?

Is all that data in that created ADIF?

Are you using the File / Import ADIF File and following the steps for that ADIF import process?

It could be that the created ADIF file may not be using a standard ADIF format for all the fields. Lele follows the most current ADIF standard so fields should match, but we can't control what other APPs/Vendor do when they create ADIF files if they don't follow the same industry wide standar.

If you open those created ADIF files with the (free) program called ADIF Master are those fields in that file and properly filled out?

[G0BON]

Hi KI5IO
The ADIF was imported from an Android App "VLS Logger".
For comparison I put a few sample lines into another Android App "Fieldlog" and that imported okay with the fields filled in correctly so there must be something wrong with the VLS logger adi file generation.

I'll try the ADIF master as you suggested. At least its pointed the roblem to the app and not Log4OM
Thanks for your help in getting to the bottom of this.

[G0BON]

I finally found the error.
Importing from one looger app I had the freq as 7100Mhz the other app 7.100Mhz. So missed the decimal point in one of the log entries.
When importing the adi into log4om the freq entry of 7100mhz messed up the band fields for 40mtr.

[DF5WW]

Check the Frequency .... 7120000 is wrong. Frequency in kHz is 7120 the 3 zeros for Hz are in the seperate Box. A decimal point is also
wrong so the Frequency is kHz only and there´s no decimal in.

[KI5IO]

Hi KI5IO
The ADIF was imported from an Android App "VLS Logger".
For comparison I put a few sample lines into another Android App "Fieldlog" and that imported okay with the fields filled in correctly so there must be something wrong with the VLS logger adi file generation.

I'll try the ADIF master as you suggested. At least its pointed the roblem to the app and not Log4OM
Thanks for your help in getting to the bottom of this.

Ivan,

Very good to hear and glad you found the hiccup. Also appreciate the follow-up as that helps all of us who may run across similar.