Hi all,
I made today a QSO with CT9/IZ2DPX. Wl32 recognizes the call DXCC 259, Svalbard. Via File/Maintenance I did update the DX-prefix database and after restart Wl32 a Chck-robot action. The call is still connected to Svalbard (259) and not Madeira (256). BUT: in the cluster the call is recognized as Madeira!!
How can I correct this?
73, Martin
PA0MJM
CT9=Svalbard :-(
CT9=Svalbard :-(
Martin,
Try double clicking on the callsign box at the upper left of the Winlog32 screen, with your erroneous CT9 contact loaded. That should allow you to change the country.
Mike
K2CBI
Try double clicking on the callsign box at the upper left of the Winlog32 screen, with your erroneous CT9 contact loaded. That should allow you to change the country.
Mike
K2CBI
CT9=Svalbard :-(
Tnx, Mike. That did the trick!
Learned something new today in wl32
73, Marin,
PA0MJM
Learned something new today in wl32
73, Marin,
PA0MJM
CT9=Svalbard :-(
I worked him also. Looks like I need to go in and make the correction as well. I didn't even notice! Thanks for pointing it out.
73 de K2WLO John
Ex KC2WLO
73 de K2WLO John
Ex KC2WLO
CT9=Svalbard :-(
It seems my log is reading CT9 correctly. I have already uploaded all available updates for Winlog32, and at no point does it read CT9 as Svalbard. After updating your DX prefix database did you restart Winlog32? I believe you need to.
73 de K2WLO John
Ex KC2WLO
73 de K2WLO John
Ex KC2WLO
CT9=Svalbard :-(
Hi Guys.
The problem with a wrong country entity being added to the log is possible in certain instances.
It happens when a part QSO is entered into the log, and before QSO is saved, this same QSO Callsign is edited (different entity) and then not using the enter key afterwards (e.g. mouse), the QSO will still retain the original entity.
I am going to work on this in the future to fool-proof this situation.
The Log Check Robot (all options disabled) should find this sort of error in the log.
It also be fixed as described above.
73 Colin G0CUZ
Winlog32 Author
The problem with a wrong country entity being added to the log is possible in certain instances.
It happens when a part QSO is entered into the log, and before QSO is saved, this same QSO Callsign is edited (different entity) and then not using the enter key afterwards (e.g. mouse), the QSO will still retain the original entity.
I am going to work on this in the future to fool-proof this situation.
The Log Check Robot (all options disabled) should find this sort of error in the log.
It also be fixed as described above.
73 Colin G0CUZ
Winlog32 Author
CT9=Svalbard :-(
Mike, Colin,
@Mike: I did a restart after updating the DXCC-dbase.
@colin: I did a chk-robot action, but I can't remember if all the options were disabled.
Anyway, it's OK now.
Another day in the office.... eh, shack
mny tks fer all help
73, Martin
PA0MJM
@Mike: I did a restart after updating the DXCC-dbase.
@colin: I did a chk-robot action, but I can't remember if all the options were disabled.
Anyway, it's OK now.
Another day in the office.... eh, shack
mny tks fer all help
73, Martin
PA0MJM