This release - while importing a QSO with the "Deduce missing items from entity, primary subdivision, and DXCC database" option enabled, correctly determines the IOTA and STATE (tnx to Larry W6NWS) - eliminates an errorlog.txt entry when performing a callbook lookup on a one-character callsign (tnx to Ray KE3G) - automatically updates the specified Log Page Display layout file if an Item's Caption or Alignment is changed with the "automatically update layout file" option enabled - makes Scotland precede Shetland Island in the CQ Marathon progress report and submission spreadsheet (tnx to Dave G4MUL) - prevents the automatic "Update Log" function from modifying the log's "last assigned unique QSO number" - provides the ability to resequence the Unique QSO number assigned to each QSO in the log - when the Log Page Display is sorted by Unique QSO number, defaults to displaying the most recently-created QSOs (tnx to Charles ZL4DX) - when the "Optimize for realtime QSO entry" option is changed from enabled to disabled, the Log Page Display is sorted in ascending order of Unique QSO number (tnx to Charles ZL4DX) - updates the Configuration.htm, Item.htm, and LogCompletedMain.htm documentation files Note: Whenever DXKeeper logs or imports a QSO, it assigns that QSO a unique QSO number by incrementing a "last assigned unique QSO number" setting saved within each log. DXKeeper's "Update Log" function is automatically invoked by a DXKeeper upgrade that adds one or more new items to each QSO. There was a longstanding defect in this "Update Log" function: it erroneously set the log's "last assigned unique QSO number" to the number of QSOs in the log. When applied to a log in which one or more QSOs have been deleted, the result was that some QSOs created after the "Update Log" function was run would be assigned non-unique QSO numbers. If you haven't been using Unique QSOs numbers, then no action is required. If you have been using Unique QSO numbers, then you now have the option of directing DXKeeper to assign a new Unique QSO number to each QSO in your log by clicking the new "Reset Unique #s" button at the bottom of the Configuration window's Log tab. DXKeeper will assign each QSO a Unique number based on the QSO's order of occurrence: the earliest QSO in your log will be assigned Unique QSO number 1, the next will be assigned number 2, etc. Invoking the "Reset Unique #s" function will ensure that each QSO has a Unique QSO number, but will - lose the order of entry for all QSOs logged to date, because the newly assigned QSO numbers will be in order of occurrence - potentially change the Unique QSO numbers logged with your QSOs DXKeeper 9.1.4 is available via the DXLab Launcher and via 73, Dave, AA6YQ