Note: When you first run DXKeeper 11.1.6, it will prompt you to backup your log, and then proceed to increase the width of the latitude and longitude items in each of your log's QSOs so that degrees, minutes, and seconds can be stored. Be sure to backup your log, as earlier versions of DXKeeper will not be able to open it after the latitude and longitude items are increased in width. This release - prevents eQSL.DownLoadLogPageeQSLImages from terminating when processing a QSO that doesn't specify needed information (tnx to Manfred DB3KE) - ensures a reasonable minimum height and width for the QSO Comment window (tnx to Jack KK5ZY) - includes an updated DOK award file (tnx to Koen ON7RK) - properly parses the LotW Station Data file when an Australian State is specified (tnx to Hilary VK2IUW) - considers a QSO's callsign to be an LotW Member if that callsign has uploaded QSOs to LotW after the QSO began (tnx to Joe W4TV) - provides the option of handling LotW QSL detail inconsistencies by including them in the report displayed when the "Sync LotW QSLs" or "Update from LotW" operation completes (tnx to Peter N5UWY and Rich VE3KI) - displays the full TQSL version number in the TQSL panel on the "QSL Configuration" window's LotW tab - updates TQSL error code descriptions to reflect rejection due to invalid QSOs in the batch to be digitally signed and uploaded (tnx to Larry K8UT) - when TQSL rejects QSOs to be uploaded, displays the contents of the LotWResults.txt file  - when processing LotW's report of a confirmed QSO [initiated by "Sync LotW QSLs" or "Update from LotW"], determines whether LotW considers the QSO an exact "mode match"; if so, adds an "M" in the QSO's "LotW Confirmation" item; if not, mentions the absence of an exact "mode match" in the after-action report (tnx to Joe W4TV and Mike K1MK) - includes an "LotW Mode" column in the WAS progress report that displays an = if LotW considers that QSO an exact "mode match" (tnx to Joe W4TV and Mike K1MK) - if the Marathon Progress or Submission report is initiated with the Log Page Display filtered, informs the user and provides the opportunity to clear the filter before generating the report (tnx to Norm W4QN) - interprets CTRL-P in the Capture window or in panels on the Main window's "Log QSOs" tab with no DXCC prefix selected to mean "perform a lookup operation and log the QSO" (tnx to Ralph K0IR and Peter W2IRT) - interprets CTRL-ALT-F in the Filter panel textbox to mean "set QSL_RCVD to 'Y' and set the QSL Rcvd Date to today without setting QSL_SENT to 'R' " (tnx to Peter W2IRT) - expands latitude and longitude items to display seconds as well as degrees and minutes - provides and QSL substitution commands that are replaced by the latitude and longitude in degree, minute, and second notation; the existing and QSL substitution commands continue to be replaced by the latitude and longitude in degree and minute notation. - when performing a lookup operation in the Capture window with "Previous QSO Display" enabled and a Callbook configured, updates the QSO's latitude and longitude with Callbook data if the grid square extracted from a previous QSO is not confirmed, if that previous QSO's location is not specified to the second, and if the Callbook's latitude and longitude are specified to the second - when the CBA function is invoked on the Main window's "Log QSOs" tab, updates the QSO's latitude and longitude with Callbook data if the QSO's grid square is not confirmed, if the QSO's latitude and longitude are not specified to the second, and if the Callbook's latitude and longitude are specified to the second - supports "to the second" latitude and longitude positions in WinWarbler version 7.7.0 and later) - provides "to the second" latitude and longitude positions to DXView version 3.8.0 and later) - updates Configuration.htm, Items.htm, KeyboardShortcuts.htm, LotW.htm, Progress.htm, QSL.htm and QSLConfiguration.htm documentation files Notes: 1. When you first run DXKeeper 11.1.6, it will prompt you to backup your log, and then proceed to increase the width of the latitude and longitude items in each of your log's QSOs so that degrees, minutes, and seconds can be stored. Be sure to backup your log, as earlier versions of DXKeeper will not be able to open it after the latitude and longitude items are increased in width. 2. When you and your QSO partner upload information about your QSO to LotW, LotW will generate a confirmation for each of you if your uploaded information matches. In particular, the mode you each upload must belong to the same "Mode Group": CW, DATA, IMAGE, or PHONE. Some variants and endorsements for the ARRL's Worked All States Award require the modes in the uploaded QSO information to match exactly: if you upload the mode as JT9 and your QSO partner uploads the mode as DATA, an LotW confirmation will be generated, but this confirmation won't count towards the WAS "mode-indicated" Digital award. Yesterday, LotW began making "exact mode match" information available to applications like DXKeeper. During a "Sync LotW QSLs" or "Update from LotW" operation, DXKeeper 11.1.6 will insert an M into the QSO's "LotW Confirmation" item if an exact Mode Match is present; you can use this to filter appropriately filter the Log Page Display before generating a WAS Progress report for a variant or endorsement that requires exact mode matches. The WAS Progress report now includes a "Mode Match" column that displays an = if the QSO's LotW mode match is exact. DXKeeper 11.1.6 is available via the DXLab Launcher and via 73, Dave, AA6YQ