Build 8726 - Released November 22, 2023
- Crystal Reports has been removed. All legacy reports (and there were 40+ reports that were nearly 20 years old) have been rewritten using Microsoft SQL Server Reporting Services (SSRS). This will not only simplify the setup process and reduce the size of the download package, it is also a necessary step in the process of porting SWLog to arm64. For those upgrading, the Crystal Reports back-end program can be removed via the Add/Remove Programs feature in Windows.
- Fixed a bug in the ARRL LoTW upload form where the default date range was not correct.
Build 8717 - Released November 12, 2023
- When exporting ADIF files, excluding the comments field will also exclude tags. This will keep any personal information from being transmitted externally.
- Added a form to map continents to QSOs. This field is almost always empty or incorrect for stations outside of the US and Canada.
- The two dozen or so reports that were written in Crystal Reports are being rewritten in SSRS (SQL Server Reporting Services). In this release, four reports have been rewritten. This is a somewhat slow process and will continue over subsequent releases until no Crystal Reports remain. Despite its reputation, the use of Crystal Reports in SWLog has been remarkably stable for the past 20 years. With the advent of Windows on ARM and its expected increase in usage over the coming years, a large back-end effort is underway to move away from hard-coded x86 and x64 code. Crystal Reports is not available on ARM and thus would run in emulation. That is not desirable.
- Another season change, another issue with AOKI schedules. The file that was used for several years for the schedules was absent from the B23 download file. The import routine had to be refactored to work with another file format.
- Added the ability to group the individual ADDX, AOKI, EiBi, HFCC, ILGRadio, and SWSkeds schedule databases.
- Modified the import of FCC Amateur data to include data from the HD.dat file.
Build 8709 - Released November 5, 2023
- Fixed a bug in the ARRL Upload form where the wrong date was being used to populate the start datetime picker box. Now the form correctly shows the proper start date from when the last log was uploaded.
Build 8703 - Released October 29, 2023
- An automatic check for update will occur weekly. Manual checks can still be run from the About form, which can be found in the Application Menu.
- The Browse form for amateur logs now shows an indicator for those logs that have been confirmed by physical QSLs, assuming that the QSLs have been scanned and added.
- Various VARA modes have been added to ADIF 3.1.4. Adding these to the program and re-mapping the ad hoc VARA mode that was temporarily used. Logs that have been marked as VARA will be migrated to DYNAMIC / VARA HF.
- Fixed mappings for the Democratic Republic of the Congo, South Sudan, and Yemen in a world map. These had the incorrect ITU2 codes, so they appeared blank on the map.
- With support for ADIF 3.1.4, the new VarAC 8.2 program has changed how it sends ADIF entries and packets from a mode of VARA to a mode of DYNAMIC and a submode of VARA HF. Altered the UDP and ADIF logging code to reflect this change.
- DXCC changes can be processed by downloading the CTY.CSV file from AD1C.
- Support for the Griffin Powermate knob added to Radio Control Server. To see the specific mappings, check the documentation.
- In the Analytics area, the DX Tracker section now supports tracking progress against certificates like the ARRL DXCC and ARRL WAS.
- In the Analytics area, added two new forms to view QSOs by grid squares.
- Many small enhancements and bug fixes.
Build 8675 - Released October 2, 2023
- The Monitor WSTJ-X/JTDX Decodes form can now issue commands to WSJT-X to clear the content panels or halt a current transmission. The command to initiate a QSO has been in the form for a while, but one had to double-click on the row. So the feature was rather hidden. Now a TX button is on each CQ call to make this more obvious. All of these commands work with WSJT-X. Unfortunately, JTDX only supports starting a QSO. So when JTDX is detected, the unsupported features are disabled.