On 13-Nov-17 08:06, Ian Fugler wrote: > Bud > > I have exactly the same issue. It does not seem to happen every time and I > cannot ascertain a sequence of searches that triggers it. I have to > re-start DX4Win and then it works. I can confirm that. It's not just the callsign search, but others as well (DXCC, etc.). Restarting DX4Win fixes it. WA7AA