This release - won't submit a QSO to LoTW if its RX Band and RX Freq items are inconsistent (tnx to Joe KC5KIN and Kent N6WT) - when directed by another application to log a QSO and upload it to LoTW, sends the correct BAND_RX to LoTW (tnx to Joe KC5KIN and Kent N6WT) - removes the NPOTA progress report - includes a *preliminary* ARRL Grid Chase progress report generator (see note 1 below) - updates the Progress.htm documentation file Notes: 1. The ARRL's "2018 International Grid Chase" is described here: During this year-long event that begins on January 1, 2018, points are issued to gridsquare-band-mode combinations confirmed via LotW on a month-by month basis. For example, if you receive an LoTW confirmation for a QSO with CM87 on 20m CW during January, you will receive additional points for receiving LoTW confirmations of QSOs with the same grid square on 20m phone, 40m CW, and 40m phone during January. If you receive an LoTW confirmation for QSOs with CM87 on 20m CW, 20m phone, 40m CW, and 40m phone during February, you'll earn 4 more points. DXKeeper tracks "Grid Chase" progress on the bands from 160m through 23cm in the CW, Digital, and Phone modes as defined by the event rules. DXKeeper's "Grid Chase" progress report is generated by clicking the GC button in the "Other progress reports" panel on the Main window's "Check Progress" tab. The generated progress report displays - Worked, Confirmed and "Grid Unconfirmed" grid-band-mode counts for each month of the current year up to the current month; "Grid Unconfirmed" refers to a grid square in a QSO confirmed via LotW whose LotW confirmation does not specify the grid square. - Year-to-date Worked, Confirmed and "Grid Unconfirmed" grid-band-mode counts - A band-vs-mode matrix for each grid square worked or confirmed during the current month Running the Grid Chase progress report also sends an SQL expression to SpotCollector that when invoked will hide grid-band-mode combinations worked or confirmed via LoTW during the current month. If SpotCollector is running, its "Accept SQL Filter Updates" option is enabled, and an SQL filter named GC has been defined, SpotCollector will update the SQL for the GC filter, and invoke it. This is the same mechanism employed for NPOTA. The Grid Chase progress report generator is preliminary for three reasons: A. The format of the progress report is still open to improvement. B. The SQL filter sent to SpotCollector does not accurately select digital modes: - only SSB counts as PHONE (AM and FM should also count) - any active DX station whose mode is not CW or SSB is assumed to be Digital C. the SQL expression generated is quite long; while the upper limit for SQL expression size has not yet been reached, the SQL expressions generated late in a month might fail to execute on some user systems. For example, I've worked/confirmed 11 grid squares this month; here's the SQL expression that DXKeeper currently generates: (not(((mid(dxgrid,1,4)='DM72')and(((Band='40M')and(Mode<>'CW')and(Mode<>'SSB'))))or((mid(dxgrid,1,4)='EM78')and(((Band='160M')and(Mode<>'CW')and(Mode<>'SSB'))))or((mid(dxgrid,1,4)='IN53')and(((Band='80M')and(Mode='SSB'))))or((mid(dxgrid,1,4)='IO91')and(((Band='160M')and(Mode='CW'))))or((mid(dxgrid,1,4)='IO92')and(((Band='80M')and(Mode='SSB'))))or((mid(dxgrid,1,4)='JN05')and(((Band='160M')and(Mode<>'CW')and(Mode<>'SSB'))))or((mid(dxgrid,1,4)='JN19')and(((Band='160M')and(Mode<>'CW')and(Mode<>'SSB'))))or((mid(dxgrid,1,4)='JO02')and(((Band='80M')and(Mode='SSB'))))or((mid(dxgrid,1,4)='JO60')and(((Band='160M')and(Mode<>'CW')and(Mode<>'SSB'))))or((mid(dxgrid,1,4)='KN69')and(((Band='160M')and(Mode<>'CW')and(Mode<>'SSB'))))or((mid(dxgrid,1,4)='KO25')and(((Band='160M')and(Mode<>'CW')and(Mode<>'SSB')))))) and (len(DXGrid)>0) and The solution to the latter two issues is to extend SpotCollector's Spot Database by adding 3 new fields, each with 1-letter names: G: contains the first 4 characters of the existing DXGrid field B: contains a 1-digit code that specifies the band M: contains a 1-digit code that accurately specifies the "Grid Chase Mode" (e.g. "Digital" will be computed as "counts for ARRL DXCC Digital awards", and "Phone" will include SSB, AM, and FM) This will greatly reduce the length of the SQL expressions generated by DXKeeper's Grid Chase progress report. If you worked two grid-band-modes during the current month, the optimized SQL expression would look like (not(((g='DM72')and((B=2)and(M=1)))or((g='CM87')and((B=1)and(M=2))))and(len(G)>0)and I'll be extending SpotCollector along these lines, and then updating DXKeeper again to emit the optimized SQL as described above. In the meantime, if you're planning to participate in the 2018 Grid Chase, you can use DXKeeper 14.3.9 to practice; it will display your Grid Chase progress for 2017, and direct SpotCollector to locate grid-band-mode combinations not worked during the current month. 2. Update your firewall and anti-malware applications to consider this new version of DXKeeper to be "safe" 3. If this upgrade doesn't work correctly, see the "After an Upgrade" section of 4. After upgrading, to revert to the previous version of DXKeeper, see DXKeeper 14.3.9 is available via the DXLab Launcher and via 73, Dave, AA6YQ