Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No DXCC (#) is not a DXCC point! #165

dl7oap opened this issue May 4, 2019 · 1 comment


None yet
1 participant
Copy link

commented May 4, 2019

ok1rr observed the following:

No DXCC (#) is not a DXCC point!

while preparing my application for CW Excellence Award by TBDXC ( I set up filter to date from 2018-10-01 till today, mode CW, sort by Call and group by dxcc_ref. The resulting score contained also JX7X wich was a pirated call and has DXCC ref. = #.

This means that # in statistics counts as a regular DXCC point. It should be fixed!


This comment has been minimized.

Copy link
Contributor Author

commented May 4, 2019

Startpoint: fFilter.pas procedure TfrmFilter.btnOKClick
column 419
case cmbGroupBy.ItemIndex of
1 : grb_by := 'GROUP BY dxcc_ref';

and colum 448
tmp := 'SELECT * FROM view_cqrlog_main_by_qsodate WHERE ' + tmp + ' ' + grb_by +' ' + OrderBy;

in the view view_cqrlog_main_by_qsodate table cqrlog_main is joined (no inner, no outer join) with table dxcc_id via adif.

With squirrl "select * from view_cqrlog_main_by_qsodate" shows '!' in field dxcc_ref for qsos which have adif = 0

QSO List Filter seems to be ok, because a "group by" on dxcc_ref in QSOList-Gui should show the real world of the logged qso.

In the QsoList-Gui are 3 counter "QSO in log", "DXCC" and "DXCC CFM".
Is this bug related to the field "DXCC" and "DXCC CFM" ? Then we have to search where frmMain.pas lblDXCC and lblDXCCCmf are calculated and filled when a filter gets active.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.