Previous QSO not showing in area above New QSO fields

12 posts / 0 new
Last post
W4AOX
Previous QSO not showing in area above New QSO fields

Hello.

the issue I am having is that previous QSO's are not populating the area above the new QSO fields. Also, all of the fields in the previous QSO section have been made to say "Title" and a few have some unrecognized characters. EDIT: I have a screen capture at the following link - https://postimg.cc/wtBS3tqc

I've noticed this issue the other day and have not found a solution yet.

Has anyone ever seen this before or can offer some guidance as to what may be causing this to happen?

Thanks in advance.

--
Jim - W4AOX

DL3LAR
Previous QSO not showing in area above New QSO fields

Hi,

QSOs are only shown a few days. If your entry is too old, it's not shown any longer. You can change for how many days qso's are listed:
Preferences -> New QSO
Checkmark 'Show recent QSO records for last nn days'
I set it to 30 days.

Remark: sometimes the list is not population correctly, in this case, I enter some call in the call-field, press 'TAB' and wipe it again with 2x 'ESC'.

73, Rolf

W4AOX
Previous QSO not showing in area above New QSO fields

Thanks for the reply Rolf.

My setting for:
Preferences -> New QSO
Checkmark 'Show recent QSO records for last nn days'
Is also set for 30 Days.

What I don't get is why the fields at the top are only saying "title" and not qsodate, callsign, freq, mode, etc.

The QSO List is listing all fields just fine so I am thinking that something is keeping those fields from being populated in the NEW QSO window and that is keeping recent QSO's from showing up because the fields aren't correct.

Short of a uninstall/reinstall I was hoping it would be something simple but I am not finding anything about this particular problem.

File: 

DL3LAR
Hi Jim,

Hi Jim,

looks like something is wrong. I'm using the same cqrlog version, but I don't have this problem.
Maybe someone else with deeper knowledge can help further ...

73, Rolf

G4LNA
Hi Jim,

Hi Jim,

Have you tried backing up your log book, then generating a new one and importing you data into the new log?

G4LNA
If that doesn't work Jim then

If that doesn't work Jim then it might be some corruption in your config file which should be fixable, let us know.

W4AOX
I have tried a new log from

I have tried a new log from my latest back up as well as a back up from before I noticed the problem and it has the same results so it sounds like a corrupted config file.

I will look into that and see if I can find an issue there.

Is there anything specifically I should be looking for, in case I don't recognize the problem by glancing through the config file?

G4LNA
Hello Jim,

Hello Jim,

Yes, if I remember how to do it you need to export the config file. Open the CQRLOG you will see a Utils button. Click on the button, choose Configuration -> Export. Save the file to somewhere where you can find it. It is an ini file, if you open it in something like Pluma you are looking for [frmNewQSO_dbgrdQSOBefore] in Pluma it will be line 806 or towards the very bottom of the file, it should look something like this:

[frmNewQSO_dbgrdQSOBefore]
=60
=60
=60
=0
=0
=0
=0
=0
qsodate=83
time_on=70
time_off=61
callsign=111
freq=117
mode=76
rst_s=53
rst_r=60
name=118
qth=120
remarks=410

This is a copy of my own ini file, the first line is the heading and after the equals sign is the column width, if you see a load of gobbledygook in your file try replacing it with the above and re-import it and see if that helps. I have had to do that myself a few times when things get messed up for what ever reason, I'm probably the problem because I do like to play around with things, I can't leave alone :)

G4LNA
Here is a better list of what

Here is a better list of what should be in there:

[frmMain_dbgrdMain]
id_cqrlog_main=0
qsodate=110
time_on=77
time_off=60
callsign=125
freq=110
mode=88
rst_s=78
rst_r=63
name=177
qth=103
qsl_s=0
qsl_r=0
qsl_via=0
iota=0
pwr=0
itu=0
waz=0
loc=0
my_loc=0
county=0
award=0
remarks=337
band=0
dxcc_ref=0
qso_dxcc=0
profile=0
idcall=0
state=0
lotw_qslsdate=0
lotw_qslrdate=0
lotw_qsls=0
lotw_qslr=0
cont=0
qsls_date=0
qslr_date=0
club_nr1=0
club_nr2=0
club_nr3=0
club_nr4=0
club_nr5=0
eqsl_qsl_sent=0
eqsl_qslsdate=0
eqsl_qsl_rcvd=0
eqsl_qslrdate=0
qslr=0
country=0

W4AOX
Hello Paul,

Hello Paul,

I think we are getting closer to the problem.

AS you described, here is what I found after exporting the .ini file:

[frmNewQSO_dbgrdQSOBefore]
=`1ÖTÈfv
=Z

However, after copying your example and saving the file and importing it, nothing changed. I closed the program, re-opened it and nothing changed,

So I exported, saw the same gobbledygook as before, replaced with your example again, saved then imported again and then immediately exported, only to find the changes that were imported did not stick. In fact, I got EXACTLY what I had gotten before, letter for letter.

I will doing some more playing around with it. I may just have to try to run a repair or just do a complete uninstall/install, after I make sure to safely locate a back up ;)

But thank you for your help.

oh1kh
configuration export/import

Hi!
I have not followed properly this thread but understood that you are trying to restore missing columns by fixing the log's confiuration with export/edit/import.

Importing of log settings does not always work. just do not know why (must be studied at some time). See thread https://www.cqrlog.com/node/2111

I suggest that you do a new log like https://www.cqrlog.com/comment/6716#comment-6716 says using the fixed log settings ini file.
After that import all qsos from adif and see if everything works.
Could it help?

Sorry if I have not understood the problem.

--
Saku
OH1KH

G4LNA
Hi Jim,

Hi Jim,

That looks like where the problem is, an uninstall/reinstall could well cure things. As a matter of interest I usually backup to Dropbox, I know then I've always got a copy somewhere on one of the other computers or on the cloud.

Good luck, let us know how you get on.