www.dl2rum.de

I have a contact in my log with a Russian station that shows incorrect zones and DXCC. The station is a special call, UE95GA. Based on the callsign, the zones are incorrect and the DXCC shows UA0.

The station was operating in Moscow oblast, region R3D. I was able to change the zones in the contact to 16 and 29, but I don't see a way to change the DXCC to UA.

How can I edit the DXCC value in the contact?

You can't. See here: http://dl2rum.de/RUMlogNG/docs/en/pages ... _CLDX.html
Note also Menu-->Logbook-->Recalculate DXCCs once you updated your database.

DL2RUM wrote:You can't. See here: http://dl2rum.de/RUMlogNG/docs/en/pages ... _CLDX.html
Note also Menu-->Logbook-->Recalculate DXCCs once you updated your database.

Thanks, Tom. That solved the problem.

I forget to occasionally update these things. Thanks very much for the reminder!

73,

Hi Tom, coming back to this thread. I've run into a some calls that seem to have a similar problem. For example:

AD0S/KH5K/K is a Clublog whitelisted call for Kingman Reef. Even with an update of DXCC data and a recalcute, RumlogNG is still mapping this to "K". Curiously it is mapping the IOTA (OC-096) correctly.

As suggested, I added it manually to the callsign exceptions table and recalculated DXCC and the DXCC was changed, correctly to KH5K.

I have several other whitelisted, but non-conformist calls to add. My question is does this custom exceptions table get over written next time I update?

73 de David KT5V

It seems to me the correct callsign should be AD0S/KH5/K
There is an exception for this, but not for AD0S/KH5K/K

You own exceptions are always used first!

Thanks Tom - even your great program can't help with my typos!