Prefix bug

[IW3HMH]

A small note...

ADIF protocol has some major drawbacks.
1) the ADIF Group is lead by a logging software developer. Almost everything on that standard is made to comply needs of his specific logger software, even fields without sense or without any clear indication of use.

2) the ADIF standard is something that you can see, maybe, in the 40% of loggers. other 60% follow their own rules, and ADIF is likely something annoying that user requires.

3) ADIF standard is everything but a standard. Many of the information needed to manage an award (like DXCC) is missing or unuseable or, worse, incomplete. This works probably well on the logger we mentioned before, but I have doubts. There is not a clear indication on how to use some fields in the ADIF protocol. Some information is hard coded and needs a new revision of the protocol to be included (check satellite lists...)

4) Complying to ADIF standard means you can export all your data and migrate towards another software in every moment.

Point 4 is the main reason about lack of ADIF compliant export from the larger number of softwares (you usually have a highly partial export). On the other side i strongly think that logs are properties of the operators, and software is a benefit, not a constraint. Log4OM is (so far, as far as I know) the only software on the "market" that exports all 106 ADIF fields (even fields that we don't actually manage but we import from adif files, if they exists) plus some "program fields" that i set to keep track of awards and can be useful when you reload your database from an ADIF export.

Try exporting your data from Log4OM and from any other software you know. Let me know on how many software you can rebuild FROM ADIF your informations regarding received QSL cards, as example.