Can't update My ITU and My CQ in original log file

[W4EBB]

On 2/13/2020 I began the conversion from V1 to V2 and did the adif conversion and load.

On 2/15/2020 I came up under V2.

Now I have discovered a problem with the My ITU (my bad).

I have also discovered that I can not update a QSO with a bad My ITU in the 02/13/2020 and back part of my log file. Because the edit QSO only allows a 6.

In the 2/15/2020 and forward part of the log file a 6,7 or 8 is allowed.

It is the same situation with My CQ but I do not have a problem there.

I looked around in the forum and the user guide but I did not find anything.
I am on 2.4

Help!

Charlie
W4EBB

[KD0ZV]

Charlie,

I would use the QSO manager to do that. Make a backup of your log by exporting an ADIF.

Under QSO manager click the update QSO tab

Select MyITUZone and set the value to what you want and update.

Once again make a backup first.

Rich

[W4EBB]

Rich,
Sorry I did not say that but that is what I was doing.

It updated all the ITUs until it got to 2/13/2020 and did not update any from there on.

Charlie
W4EBB

[KI5IO]

Rich,
Sorry I did not say that but that is what I was doing.

It updated all the ITUs until it got to 2/13/2020 and did not update any from there on.

Charlie
W4EBB

Charlie,

Did you happen to have a date range set in the adjacent tab called "Search QSO" ?? You might have accidently had a from/to date range set.

[W4EBB]

I did have a date range set.

From 01/01/2015 (the beginning of the file) to 02/13/2020 (the end of the original log file).

I then clicked select and 7600 records were selected.

I then switched tabs and selected myituzone and gave it a value of 8.

Then I clicked update - it ran for bit - but no records were updated.

I think it has something to do with if you click edit qso on one record the only choice you have is 6 and when I try to make it an 8 it is invalid. As I said earlier, on the records 02/15/2020 and up the available choice is 6, 7, or 8.

Charlie
W4EBB

[NN7D]

Charlie,

I have been able to replicate this issue, in V2.5.0.0. One thing which is going on is that the program is doing a quality check and will not allow the zone changes if the My Country field is not set correctly. I don't think that should be happening with a Mass update, but I may be outvoted on that one.

But in any case, I've also had records which were skipped from updating where My Country was set correctly. So we have that to fix.

Thanks for reporting.

Doug
W7DRM

[NN7D]

Charlie,

The work around (or maybe correct way) to do this is to first set all your QSO records MyCountry data to United States via QSO Manager Update QSO tab. Once that update is finished, reset your MyCQZone and MyITUZone data the same way. This worked for me.

Doug
W7DRM

[W4EBB]

I will give that a try and report back.

[W4EBB]

Hey Doug:

That was it. I fixed the United States, then fixed the ITU. I wondered if I could do both in one pass but was not up to trying.

Thanks so very much!

Charlie
W4EBB