Page 2 of 2
Re: "Award refs." can't be removed
Posted: 17 Aug 2020, 19:51
by LB4MI
Hi,
the problem is still present in v.2.8,
I was referring to your e-mail the 7'th of July regarding this issue,
Best regards,
LB4MI
Re: "Award refs." can't be removed
Posted: 30 Sep 2020, 16:22
by LB4MI
Hi,
the issue is the same also in version 2.9.0.0
I can't remove the Award Reference
(I tried to upload a video at 2 megabytes to show the issue, but get error message that file is to large)

- log4om 2.9.0.0.jpg (111.04 KiB) Viewed 3007 times
Recent entries does not have this problem, but those QSO's entered a year ago has.
73.
Re: "Award refs." can't be removed
Posted: 30 Sep 2020, 16:24
by G4POP
LB4MI wrote: 30 Sep 2020, 16:22
Hi,
the issue is the same also in version 2.9.0.0
I can't remove the Award Reference
(I tried to upload a video at 2 megabytes to show the issue, but get error message that file is to large)
log4om 2.9.0.0.jpg
Recent entries does not have this problem, but those QSO's entered a year ago has.
73.
Grrrrrrrrrrrrrrrrrrrrrrrrrrrrr!!!!!!
Re: "Award refs." can't be removed
Posted: 30 Sep 2020, 16:49
by IW3HMH
I can't understand the difference from old and recent qso's...
can you pack up your database into a zip file and send it to me at lele (at) pisto.it ?
I also need a reference to find this QSO
Re: "Award refs." can't be removed
Posted: 09 Nov 2020, 16:00
by IW3HMH
Hi Helge
the COMMENT field of your QSO contains a SOTA reference.
During QSO save the whole QSO is parsed for references (that could be related to newly added awards) and the reference printed on the COMMENT field is identified again, and then reinserted in the QSO itself.
Remove the comment, then the reference and save

Re: "Award refs." can't be removed
Posted: 19 Nov 2020, 18:42
by LB4MI
SOLVED
Hi,
thanks for the reply and your e-mail on the same topic,
I've cleaned up all of my comments now, and that did indeed solve the problem!
I was not aware of the "power" of the Comment/Note field for looking after references, but now I know
Thanks for looking into that, hopefully this can be of use of someone else having the same issue later someday.
73,
LB4MI