73 to everyone!
I ask a simply question..
I had QSOs with SOTA references from DXCC entities Crete and Dodecanese.
The software that I use, LOG4OM, doesn’t accept SOTA entries from this entities.
I have to replace them with GREECE.
If I then send the log to CLUBLOG or other ONLINE LOGS, they suggest correcting the entities because they’re incorrect..
I understand very well that for the SOTA program the DXCC is not so important, but the summits you as worked..!
Is there any way to fix this?
Tnx !
73’s Giuliano in3klq
Vy Tnx Joe for your reply!
Pse see this post on the Forum Log4om
(You don’t need to register to read it)
Maybe I can make my post clearer. https://forum.log4om.com/viewtopic.php?t=10273
If I understand correctly than they (LOG4OM) use the SOTA association as the DXCC country name on import instead of rechecking the callsign (prefix) and assign the DXCC like that.
Yes there is only one association for Greece, SV which includes SV5 and SV9. But SV5 and SV9 are separate DXCC. Greece was added to SOTA right near the start, it is AssociationID=9 and if you think the first six were G,GM,GW,GD,GI & EI you can see how near the start SV was. Probably now SV9 would be a separate association
Giuliano, if you still have questions, you could ask in the Log4OM forum. The Log4OM (and Log4OM2) support team very much appreciates being asked questions directly.
BTW, I use Log4OM2 in the home shack and have been very happy with it - talks to the rig in the shack without a problem. Being across the pond, I would be thrilled to have the opportunity to worry about how it would handle SOTA contacts from Crete and Dodecanese!
