TX Power not being imported

[ZL2KE]

Same problem seen with a recent import from HRD Logbook v6.1....power is save as ##.###. As a result, nothing is saved in the power field.

73 Dave K3DCW

When importing from eQSL and SKCC Logger, there were ###### marks in the QSO Date column when opening
the CSV file in MS Excel - but when I used Open Office Org to open the CSV file, all was good.

73 Steve ZL2KE

[G4POP]

Same problem seen with a recent import from HRD Logbook v6.1....power is save as ##.###. As a result, nothing is saved in the power field.

73 Dave K3DCW

When importing from eQSL and SKCC Logger, there were ###### marks in the QSO Date column when opening
the CSV file in MS Excel - but when I used Open Office Org to open the CSV file, all was good.

73 Steve ZL2KE

In spreadsheets the ######### marks usually indicate that you need to widen the column width!

Most times when we see this it is because the original log program is saving the date and time in the same field instead of separate fields as dictated by ADIF.

However if you send me the ADIF file by email I will rectify the issue for you

[k3dcw]

Same problem seen with a recent import from HRD Logbook v6.1....power is save as ##.###. As a result, nothing is saved in the power field.

73 Dave K3DCW

When importing from eQSL and SKCC Logger, there were ###### marks in the QSO Date column when opening
the CSV file in MS Excel - but when I used Open Office Org to open the CSV file, all was good.

73 Steve ZL2KE

Steve,

In my case, I was using the ##.### as representative, not what actually was being exported.

HRD Logbook v6.1 exports the power using up to 3 decimal points; thus 10 watts is exported as 10.000, whereas 1/10th of a watt is exported as 0.100 and a half-watt is 0.500. Log4om won't import power of less than 1 watt...it shows up as 0 watts. They have said that it will be supported in the next version, however.

Sorry for any confusion that the "#" may have created in my post.

73,

Dave
K3DCW