2 issues:
7QAA is not recognized as a valid call. If I add a number after "Q", Log4OM recognizes the call. If I manually select Malawi in the country drop down, it allows me to store the contact.
But if I make another contact with 7QAA, the QSO Information is blank.
QSO information missing-invalid call
Re: QSO information missing-invalid call
This is an identified issue we are working on. Seems that standard rules no longer apply regarding call signs.
K7PT-Chuck "#1 Top of the Honor Roll"
Re: QSO information missing-invalid call
that's for Chuck
I was doing a check on old qsos with 9Q50ON
They have been imported by log4om as TN Republic of the Congo (412)while is Dem. Rep. of Congo (414)
it is for sure a parsing issue depending on data got from qrz .com where Dem. Rep. of Congo is written as:
//////////////////////////////////////////////////
9Q50ON Congo, Dem. Republic of flag Congo, Dem. Republic of
Special event station 50 years independence of R.D.C
Kinshasa
Democratic Republic Congo
Congo, Dem. Republic of
QSL: ON4BR
//////////////////////////////////////////////////
can you do a check ?
tnx
I was doing a check on old qsos with 9Q50ON
They have been imported by log4om as TN Republic of the Congo (412)while is Dem. Rep. of Congo (414)
it is for sure a parsing issue depending on data got from qrz .com where Dem. Rep. of Congo is written as:
//////////////////////////////////////////////////
9Q50ON Congo, Dem. Republic of flag Congo, Dem. Republic of
Special event station 50 years independence of R.D.C
Kinshasa
Democratic Republic Congo
Congo, Dem. Republic of
QSL: ON4BR
//////////////////////////////////////////////////
can you do a check ?
tnx
73 de Don IK2EGL
Re: QSO information missing-invalid call
The call, 9Q50ON, resolves correctly as DXCC code 414, Dem Rep of Congo.
Yes, I believe the way QRZ has it written is incorrect as 9Q50ON Congo. Should be 9Q50ON Dem Rep of Congo.
Yes, I believe the way QRZ has it written is incorrect as 9Q50ON Congo. Should be 9Q50ON Dem Rep of Congo.
K7PT-Chuck "#1 Top of the Honor Roll"
Re: QSO information missing-invalid call
ciao Chuck and Daniele
let me better explain the issue, as I did not before;the wrong behavior is not in intert QSO window
In fact if I insert 9Q50ON as new qso 414 dxcc is correcly associated
But if I do UPDATE INFO in the QSO archive window log4om updates it with 412 dxcc.
let me add that when I initially imported my full log all qsos with 9Q50ON have been logged a 412
I think that the problem in is UPDATE and in IMPORT functions, not in the INSERT
let me better explain the issue, as I did not before;the wrong behavior is not in intert QSO window
In fact if I insert 9Q50ON as new qso 414 dxcc is correcly associated
But if I do UPDATE INFO in the QSO archive window log4om updates it with 412 dxcc.
let me add that when I initially imported my full log all qsos with 9Q50ON have been logged a 412
I think that the problem in is UPDATE and in IMPORT functions, not in the INSERT
- Attachments
-
- 9q50.jpg (137.57 KiB) Viewed 6566 times
-
- 9q502.jpg (65.16 KiB) Viewed 6566 times
73 de Don IK2EGL
Re: QSO information missing-invalid call
Hi Terry
Thanks for your replay
Let me explain the full story on my side
I was checking on 9q qsos on some bands (cluster was telling me as missing one ) and I found a discrepancy with lotw log.
So I did a check and I found that 9Q50ON was logged as TN and not as 9Q5.
I modified all 9q50 from archive window and updated 412 with 414 dxcc.
All fine .... 414 was fine for all qso anche challenge award window was retrieving correctly all 9q5
After that I did the update info in archive window as I wanted log4om to add for me the relevant information (see the first row only) I was wissing when I imported the qso last year
Once ended the update I found again 412 dxcc instead of the 414
Can I ask you to do a test on you side too ? Tnx
Thanks for your replay
Let me explain the full story on my side
I was checking on 9q qsos on some bands (cluster was telling me as missing one ) and I found a discrepancy with lotw log.
So I did a check and I found that 9Q50ON was logged as TN and not as 9Q5.
I modified all 9q50 from archive window and updated 412 with 414 dxcc.
All fine .... 414 was fine for all qso anche challenge award window was retrieving correctly all 9q5
After that I did the update info in archive window as I wanted log4om to add for me the relevant information (see the first row only) I was wissing when I imported the qso last year
Once ended the update I found again 412 dxcc instead of the 414
Can I ask you to do a test on you side too ? Tnx
73 de Don IK2EGL
- G4POP
- Log4OM Alpha Team
- Posts: 10803
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: QSO information missing-invalid call
Don,
I entered a QSO with 9Q50ON and edited the country to "Republic of the Congo DXCC 412" and saved it as in the archive manager screen shot below
Then I highlighted the entry and clicked the "Update QSO" button on the QSO Archive manager tool bar - The entry was updated to "Dem. Rep of Congo DXCC 414" as shown in the second screen shot below.
I tried removing the country and DXCC number from the QSO so there were blank fields and then clicking the "Update info" button and again the QSO was updated to "Dem. Rep of Congo DXCC 414"
I then repeated the process but this time using the "Update" button in the "Update QSO" (Edit QSO would be a more correct description of this window) window with exactly the same result
Clearly I am missing what the problem is
.
.
I entered a QSO with 9Q50ON and edited the country to "Republic of the Congo DXCC 412" and saved it as in the archive manager screen shot below
Then I highlighted the entry and clicked the "Update QSO" button on the QSO Archive manager tool bar - The entry was updated to "Dem. Rep of Congo DXCC 414" as shown in the second screen shot below.
I tried removing the country and DXCC number from the QSO so there were blank fields and then clicking the "Update info" button and again the QSO was updated to "Dem. Rep of Congo DXCC 414"
I then repeated the process but this time using the "Update" button in the "Update QSO" (Edit QSO would be a more correct description of this window) window with exactly the same result
Clearly I am missing what the problem is
.
.
- Attachments
-
- Screenshot 2015-03-18 07.39.18.png (27.68 KiB) Viewed 6552 times
-
- Screenshot 2015-03-18 07.39.44.png (27.59 KiB) Viewed 6552 times
73 Terry G4POP
Re: QSO information missing-invalid call
Hi Terry
thanks for the test
it depends on the recorded data
If I insert today a qso with 9q50on I have the same behaviuor you have (correct)
if I work with existing data (old qsos) the wrong behaviior is reproduced (incorrect)
I will do some more investigation ; it is not a big issue, just to fully understand it and perhaps providing some indicatino for next release that Daniele is preparing 4us
thanks for the test
it depends on the recorded data
If I insert today a qso with 9q50on I have the same behaviuor you have (correct)
if I work with existing data (old qsos) the wrong behaviior is reproduced (incorrect)
I will do some more investigation ; it is not a big issue, just to fully understand it and perhaps providing some indicatino for next release that Daniele is preparing 4us
73 de Don IK2EGL
- G4POP
- Log4OM Alpha Team
- Posts: 10803
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: QSO information missing-invalid call
Don,ik2egl wrote:Hi Terry
thanks for the test
it depends on the recorded data
If I insert today a qso with 9q50on I have the same behaviuor you have (correct)
if I work with existing data (old qsos) the wrong behaviior is reproduced (incorrect)
I will do some more investigation ; it is not a big issue, just to fully understand it and perhaps providing some indicatino for next release that Daniele is preparing 4us
Send me a copy of your SQLite logbook database so that I can test it please
By email in a zip file to g4pop "AT" arrl.net
73 Terry G4POP
- G4POP
- Log4OM Alpha Team
- Posts: 10803
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: QSO information missing-invalid call
OK we found the problem when Don sent me his logbook
Our special call list had the wrong DXCC for the dates of Don's QSO’s with 9Q50OM back in 2010, this is why the old QSO’s updated with 412 but new QSO's were OK
Chuck has updated the two files and I have attached them to this post, copy them to the C:\\…….. AppData\Roaming\Logom folder and let them overwrite the original files
.
.
Our special call list had the wrong DXCC for the dates of Don's QSO’s with 9Q50OM back in 2010, this is why the old QSO’s updated with 412 but new QSO's were OK
Chuck has updated the two files and I have attached them to this post, copy them to the C:\\…….. AppData\Roaming\Logom folder and let them overwrite the original files
.
.
- Attachments
-
- historicscl.zip
- (98.94 KiB) Downloaded 267 times
73 Terry G4POP