Merge ADIF

Need help? - Post here and we will find a solution for you.
User avatar
G4POP
Log4OM Alpha Team
Posts: 7566
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Merge ADIF

Post by G4POP » 10 Mar 2019, 21:21

Perhaps you would care to post the return ADIF here as a zip file so that we can see exactly what is being imported?
73 Terry G4POP

oe3ide
Advanced Class
Posts: 34
Joined: 09 Feb 2017, 08:33

Re: Merge ADIF

Post by oe3ide » 10 Mar 2019, 22:01

Find attached a quick test sample.
1) marked QSO with QSL_RCVD = Y and QSL_SENT=Q
2) export to adif
3) set QSL_SENT = Y in 3rd-party-software
4) export to adif in 3rd-party-software
5) merge-adif in Log4OM
=> Result: QSL_RCVD = N in database
Attachments
adif.zip
(1.45 KiB) Downloaded 65 times

User avatar
G4POP
Log4OM Alpha Team
Posts: 7566
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Merge ADIF

Post by G4POP » 10 Mar 2019, 22:37

I believe it is because in the return ADIF there is not a QSL received field so without a field we would probably assume that the QSL was marked N

Alternatively there are a lot of <CRLF> annotations and these may be distorting the import because they are not normal ADIF fields.

Have you asked the author of the other program why he does not export the imported fields as received instead he is sending nothing and also why he is using <CRLF> inside an ADIF field.

Also why are you exporting as an ADIF 2xxx format instead of ADIF 3xxx?
73 Terry G4POP

Post Reply