When a callsign is entered in the new QSO interface, icons indicating if the callsign is eQSL or/and LOTW users showing up under the "Comment to Callsign box".
Where do this information come from?
The reason for asking is that my own callsign is not indicating LOTW. Even if I am marked both in qrz.com and HamQTH as lotw user.Thanks a lot for a great logging program. I have tried a numbers of other programs but CQRLOG is shooting for gold !

Hello,
 
since this is my first post on this forum, I'll first say a big "Thank You" for this very nice logging program.
 
I have one issue:
 
I had a QSO entry with mode "PSK" which was rejected during eQSL upload with "wrong mode" message.
 
I changed the mode to PSK31, but I still can not upload this QSO to eQSL, I get the message "Nothing to upload".
 
How can I upload this QSO to eQSL? I have searched the help and the forum but could not find a solution.
 
TIA and 73,
Wolfgang
 
 

Hi,
 
I'm not sure, where is problem, log soft (1.8.3) show all my qso's upload after when qso is end (Save qso) but in hamqth page cannot see that qso's. After when I upload manually my log, then all qso's is there.
 
 
 
73 de Jyrki

Hi Petr
First tests so far gone well... Seems to work with Fedora 21
and mariadb...
TNX

One of the things I would like to see is having an option to upload logs to HRDLog, Clublog, etc in the background. I have CQRLog set to automatically upload to these services after each contact. Normally this isn't a problem. But if I am on a frequency working several stations in a row, the popup window showing the status of the uploads gets in the way of me entering information about the next contact. 
 
Yes, I know that I can turn off the automatic uploading of contacts and batch upload them after I am finished. But I would really like to leave this enabled. 

Hi Petr,
 
I have found a bug in the rig-control of CQRLOG.
I changed the speed of TRX1 from 112500 to 57600 and the software stopped reporting the freq in the TRX window.
So I tried to set the Parity, Databits etc by hand, this didn't change anything.
So I restarted, nothing.
Then I set the values to default again, and this is where the bug is located, when you set everything to default, a strange thing happens, namely this:
 

Hi, 
I have occasionally issues with the log updates not going through and this frequently leaves clublog and cqrlog data in conflict. The only way to reset this is to upload full log to clublog and mark all qsos uploaded in cqrlog.
One possible fix for this could be to try to post the data to clublog several times until it succeeds. I wonder if the following change would do the trick? (in dLogUpload.pas and function TdmLogUpload.UploadLogData)
  for tr := 1 to 10 do
  begin
    if HTTP.HTTPMethod('POST',Url) then
    begin

The country files shipped with 1.8.2 contain longitudes 11 characters long for JD1(M) and JD1(O).  Since the longit column in cqrlog_common.dxcc_ref is a varchar(10), this results in an import error which prevents the deleted entities from being imported.  In turn, this results in illegal SQL queries when populating the QSO list.
 
I worked around it on my system by changing the column to varchar(12), opening the QSO list (ignoring the error), and re-importing the country files with File->Import->DXCC data.  After this, CQRLOG works perfectly again.

Hi Peter,
 
My propagation window doesn't show any indexes anymore, something wrong or that needs the be changed?
 
Thanks,
 
Bas.

I've been using Mariadb v10.x for some time, and it has shown to be very compatible with mysql based apps.
 .
I installed CQRLOG for the first time the other night and ran across an error thrown during startup. It basically said that it didnt likethe v10.x verion of mariadb but was insteadd needing/looking for the 5.5/5.6 version.
.I've installed the libmysqlclient18, which also seems to have a dependancy to mysql 5.5/5.6.
Any sense on when mariadb 10.x will be supported?
 .
thanks,
Brad

CQRlog does not work, as expected.. Namely I get following flag.
Invalid type cast.
Press OK to ignore and risk data corruption.
Press Cancel to kill the program.
And if I continue I get...
TMySQL56Connection can not work with the installed MySQL client version: Expected (5.6), got (10.0.14-MariaDB).
Press OK to ignore and risk data corruption.
Press Cancel to kill the program.
And here's debug ....
**** DEBUG LEVEL 1 ****
 
Loading libssl: /usr/lib/libssl.so.1.0.1j
Loading libcrypto: /usr/lib/libcrypto.so.10

The Space Weather Prediction Center recently revamped its entire website
The content you're looking for has likely moved to a new location.