Use DXCC ID Number on Import?

[w2nra]

I just noticed that many of my imported QSOs into RUMLog have the wrong DXCC country. All of the DXCC countries were correct in my adif file. Is there an option to use the ADIF files DXCC ID to set DXCC country rather than have RUMLog recalculate DXC

73, Art, W2NRA

[w2nra]

Whoops! I was wrong about this. My imports are fine. I was looking at the DXCC status window which showed the wrong DXCC country based on the call. But the log is correct. No problem here. Sorry!

73, Art W2NRA

[DL2RUM]

This is a complex story. When a DXCC information is found in the ADIF record set, this information will be used. When not, RUMlog will determine the DXCC. So far so good.
Problems may start, when you edit a QSO entry or recalculate the whole log, due to major changes in the DXCC table. (Last time for PJ2, PJ4 etc) Your dxcc.rsd database should reflect your current log.
This may be a problem, when you have a lot of "old" QSOs in your log (before 1978) or you worked a lot of "unregular" stations. (K4M for KH4 or TX5T for FH).
When you are sure your ADIF log (prior import) has all the correct DXCC information included, there is way to help you. In the EditDXCC application is a tool provided to extract all "unregular" calls. These information will be added to your DXCC.rsd database.
Example: You have a QSO with K8T in your ADIF log, the DXCC is stated as KH8. Normally this station would count for W. The tool adds now the call K8T to the list of unregular calls to your DXCC.rsd database.

The program is easy to use:
- start EditDXCC.app application provided in the RUMlog folder
- go to Menu-->File-->Import from ADIF
- navigate to your ADIF log file
- push the "Read" button
- differences in the logged and in the computed DXCC will be shown in a table
- push the "Write" button (before you can deselect unwanted or wrong entries)
- push the "Save" button

[K6LE]

Wow! That's a great feature Tom.

I'll have to remember that when I am suggesting that DX'ers migrate to RUMlog.

[w2nra]

<<<snip>>>
When you are sure your ADIF log (prior import) has all the correct DXCC information included, there is way to help you. In the EditDXCC application is a tool provided to extract all "unregular" calls. These information will be added to your DXCC.rsd database.
Example: You have a QSO with K8T in your ADIF log, the DXCC is stated as KH8. Normally this station would count for W. The tool adds now the call K8T to the list of unregular calls to your DXCC.rsd database.
<<<snip>>>

That's great! Then all you have to do is add the specific dates for those call signs (because they keep reissuing those calls to different places) and you're done. I would imagine that this feature would prevent you from messing things up if you did a recalculate DXCC.

Anyway good to know. I did have my adif file squared away a long time to correct DXCCs. I'll have to try your feature to make my log bullet proof.

73, Art W2NRA

[DL2RUM]

Well, you can change the start- and end date, but this is not required. The dates will be set automatically +/- few days from the QSO date.
When your log is still up to date, you can run this routine without reimporting the log. During this procedure only the dxcc.rsd database will be changed. The log will not be touched - read only.

I'll have to remember that when I am suggesting that DX'ers migrate to RUMlog.

I have to write a step by step instruction for a new comer, describing the migration. But not enough time.


Can somebody else do this?

[w2nra]

Well, you can change the start- and end date, but this is not required. The dates will be set automatically +/- few days from the QSO date.
When your log is still up to date, you can run this routine without reimporting the log. During this procedure only the dxcc.rsd database will be changed. The log will not be touched - read only.

I'll have to remember that when I am suggesting that DX'ers migrate to RUMlog.

I have to write a step by step instruction for a new comer, describing the migration. But not enough time.


Can somebody else do this?

I see what you mean. It worked great and puts in a 2 week date range. I had quite a few QSOs added. Very slick, Tom, Thank you!

I don't know if I mentioned this but I apologize if I ask too many questions. I know I should read the manual. I'm trying to catch up on my reading but summers are real busy for me (crazy cyclist). Not only am I new to RUMLog but also new to Mac and Snow Leopard and Lion and cocoaMODEM (don't work on Lion) and FLDIGI and Parallels. That's a lot of manuals to read. And I do hold down the number of questions I ask. I have lots more.

BTW Rick K6LE is the one that MADE ME TRY RUMLog, twice. The second effort worked.

73, Art W2NRA

[K6LE]

Art,

Download the latest version of cocoaModem. It works with Lion - thankfully.

Cheers,