Log4OM

I have been fortunate enough to have had a contact with FT4TA and this is how come I have noticed this problem.

When I logged the contact with that station the log window showed their grid square as LH74EC. I later found out, by looking at their QRZ page, the their correct grid square is actually LH74GC. I have edited the entry now and the correct grid shows in the previous qso window BUT, whenever I type FT4TA in the the callsign box for a new entry, the OLD incorrect grid square populates the box.

I discussed this with a friend who also worked that station..... his original entry recorded their grid as JI09GU. He too has edited his log and has the correct LH74GC grid in and again, whenever he types in the FT4TA call, the old JI09GU grid populates his grid square box.

Both of us also do not know how incorrect grids managed to populated the box's in the first place as FT4 is a brand new country for both of us and the info on that stations QRZ page is correct.... and we are both 'paid subscription' members.

Obviously, these incorrect, first entered grids are being stored somewhere and the correct info is not overwriting the bad...... does anyone know how I can fix this ???

73
John

Hi John,

the Gridsquare is grabbed from the online service you have activatet in the settigs menu. If you are a qrz xml subscriber the problem must be at qrz.com. If you are grabbing data from hamqth it could be a problem that the data there not up to date .... L4O looks on every new callsign input in the main log not to recent QSO it looks to the online service you setted up ... Or on Clublog informations if the station is listed there ... On any path something goes wrong but i think it,s not the L4O path

DF5WW wrote:Hi John,

the Gridsquare is grabbed from the online service you have activatet in the settigs menu. If you are a qrz xml subscriber the problem must be at qrz.com. If you are grabbing data from hamqth it could be a problem that the data there not up to date .... L4O looks on every new callsign input in the main log not to recent QSO it looks to the online service you setted up ... Or on Clublog informations if the station is listed there ... On any path something goes wrong but i think it,s not the L4O path

thanks for the thoughts Juergen. I have been a QRZ subscriber for many years... Log4OM is set up to do QRZ lookups. (settings/settings1/use QRZ) The information for FT4TA on their QRZ page shows the correct Grid Square but both my Log4OM and my friends both show the incorrect grid...

MORE INFO: and now it gets even stranger.... I just did updates of all the 'databases' eg, SOTA, IOTA, Country, etc etc and now, my locator gets populated with the same one as Norms, and that is JI09GU which is on the wrong side of Africa.

This problem appears to originate from the Clublog database! When the call is entered you will notice the green box displaying "Clublog" which indicates that the call was found in the Clublog file.

If you uncheck the lookup from the "Clublog Exceptions information" in the options Settings 1 menu I think you will find Log4om provides the locator that you require because only our Country file, SCL and the QRZ lookup are being used.

The Clublog exception file has two entries to FT4TA and they have different Lon/Lat references!

The entry for the 2014 expedition is Lat 15.9 Lon 54.4 which if my geography serves me well in somewhere West of Africa, whereas the older entry shows Lon 12.3 Lat 43.9 which seems to me to be correct. (Incidentally they also have the values in the two entries in opposing order in the Clublog file)

Perhaps you could send a note to Clublog?

G4POP wrote: <SOME DELETED>

Perhaps you could send a note to Clublog?

Done. I have a support ticket and am awaiting a reply. Thanks for the "how to fix" Terry.