Log4OM

Hi Terry and all,

The fault was definitely in the SOTA Associations file and I am using the latest csv of summits from the SOTA site so that's working for me. I have copied yours, Terry, and dropped it in and everything is now working fine. To prove it, I have gone back and edited my first two VK7 guys on 1/10/14 and all is working fine ...thank you so much.

John VK2YW

Hi John,
That's good, I guess I must have made a typo in the original file, these things happen

Hi Terry,

Thought I had replied yesterday but cant see it so here tis again. Your file copied from your config works fine. So problem fixed ...it was definitely that file as I tried both the summits and the associations one by one.

Remember I mentioned I could see what I described as a blue colon in the bottom LH corner of the blue bar? ...looking at it closely it looks more like an 'equal' sign if that's of any use. I saw it again when I went to edit some of the SOTA QSO's I imported from my SOTA log on SOTA.org some time back. A lot of those QSO's ..perhaps all of them have come across without their SOTA reference and so as I get time I am going back and rectifying them. But ...until I hit the update button on some of them, I see that = sign in blue on bottom left hand side of the blue bar and there is no default VK1 summit info where it would normally be on the screen. Hitting the Update button on that QSO now clears the = sign, brings back the VK1 info and then you can type in the SOTA summit into the search box and then save the QSO. Presume this is just a quirk with mine and is a result of my import of the SOTA data.

John VK2YW

John
Can you do just a normal Log4OM ADIF export (Not the SOTA Export) and send the file to me by email please?