Error Report "Bad Locator"

Need help? - Post here and we will find a solution for you.
Locked
K0TRT
Novice Class
Posts: 15
Joined: 21 Jan 2013, 19:26

Error Report "Bad Locator"

Post by K0TRT »

Hello again,
Sorry for the bother for the second day in a row.
Now it seems that when entering any call sign, or double clicking a call sign from the prop logger, the Locator Info is not there. Then when adding the contact into the log I get a "Bad Locator" error.. Any Ideas on that one ??
Thanks again in advance!
Joe WE0J
ex: K0TRT
User avatar
G4POP
Log4OM Alpha Team
Posts: 10750
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Error Report "Bad Locator"

Post by G4POP »

Hi Joe,
I will contact you by email to resolve this
73 Terry G4POP
User avatar
G4POP
Log4OM Alpha Team
Posts: 10750
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Error Report "Bad Locator"

Post by G4POP »

We accertained that this was a known issue with the small cluster window, this is the Mantis entry
0000274: Locator in small cluster but missing from QSO input pane F1
Description
This happens if the QRZ entry does not include a locator as in EA9KB or if the QRZ entry is not found as with F5LPM

I think what happens is that the cluster defaults to the country file locator if the locator is not found in QRZ and it fills the box above the cluster but not the one in the entry window.

The locator box in the entry window is only getting filled if the locator is found in QRZ
73 Terry G4POP
User avatar
G4POP
Log4OM Alpha Team
Posts: 10750
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Error Report "Bad Locator"

Post by G4POP »

In the end it was caused because Joe did not have a paid subscription to QRZ, he swapped to HamQTH and everything now works fine
73 Terry G4POP
Locked