G'Day,

Today, I was interested in what DXCC entities I had not worked and the bearing to them. So I ran the "AWARDS with Beam Heading" report using the DXCC award data.

Against my log, this report displayed an error ...



So I added LOTW_ONLY to the report variable list, and while examining the definition I noticed this report is still wanting to use the prefix table to obtain "direction" for the DXCC entity relative to my QTH. It is guaranteed to fail in Logic9.

I understand "direction" in Logic9 is calculated dynamically and obtained from the global structure "whereitis" - after the structure has been populated from the Lat and Lon in the prefix table for the DXCC entity. See this topic

So I updated the Beam Heading field expression from



to



Please note that, for "unworked" entities, I have used the "award value" to access the prefix table. The report now functions in a basic way. Clearly,for "unworked" entities, there is no call sign from which to retrieve the Lat and Lon, and the report does not make much sense for awards whose award value does not translate to a valid entry in the prefix table.

The professional programmers should stop reading here. Your blood pressure will rise if you read further.

For those of you interested in "how it works" - note the use of the functions that have "side effects" returning "nothing" to the expression. The side effects being to position the prefix table, and populate the "whereitis" structure, but return nothing to the output of the expression. Such is the skill of programming relational database reports.



I have attached my report. The reports has been renamed by adding an "underline" to the name. Just download and put it in the report sub-directory in your Logic installation - it should appear at the top of your list of reports.

I am interested in any feedback you may offer.