Importing ADIF V3 from V1
Posted: 19 Feb 2020, 13:30
Hello all,
I really want to give LOG4OM a try.
But I can not.
Problem: I exported a ADIF V3 File from LOG4OM V1 and tried to import that in V2.
About 2000 QSO's will not be imported because the Band Field is empty
Example:
WARNING: Callsign: HB9DQM/P Date: 15.02.2020 11:16:00 Band: Mode: CW QSO NOT VALID. SKIPPING IMPORT
The Band field is empty because as a SOTA Operator I import a lot of QSO by means of either CSV or ADIF import from SOTA Log Programs like vk-port-a-log and OUTD Log.
I did not care of these empty Band field in V1, there is still a correct Frequency in the Frequenc field.
What to do? Not getting this QSO into V2 is not a choice...
Can I fill Band field in V1 somehow? I don't want to do this manually..
Or is there a way to import this QSO's in V2 even if the Band field ist empty?
Thanks for your Help
73
Mark, HB99DBM
I really want to give LOG4OM a try.
But I can not.
Problem: I exported a ADIF V3 File from LOG4OM V1 and tried to import that in V2.
About 2000 QSO's will not be imported because the Band Field is empty
Example:
WARNING: Callsign: HB9DQM/P Date: 15.02.2020 11:16:00 Band: Mode: CW QSO NOT VALID. SKIPPING IMPORT
The Band field is empty because as a SOTA Operator I import a lot of QSO by means of either CSV or ADIF import from SOTA Log Programs like vk-port-a-log and OUTD Log.
I did not care of these empty Band field in V1, there is still a correct Frequency in the Frequenc field.
What to do? Not getting this QSO into V2 is not a choice...
Can I fill Band field in V1 somehow? I don't want to do this manually..
Or is there a way to import this QSO's in V2 even if the Band field ist empty?
Thanks for your Help
73
Mark, HB99DBM