<![CDATA[Swisslog's Forum - All Forums]]> https://www.swisslogforwindows.com/forum/ Thu, 16 Jul 2026 00:25:37 +0000 MyBB <![CDATA[NEW version 5.118]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1365 Sun, 12 Jul 2026 19:49:49 +0000 EA3GCV]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1365
I have just released version 5.118 implementing VERY IMPORTANT CORRECTIONS detected in version 5.117.

Please UPGRADE when asked and read the full list of corrections HERE. 

IMPORTANT!! All users executing Swisslog as administrator will lose this setting after upgrade. Remember to set it again in the Swisslog icon to avoid undesired issues.

Best 73]]>
I have just released version 5.118 implementing VERY IMPORTANT CORRECTIONS detected in version 5.117.

Please UPGRADE when asked and read the full list of corrections HERE. 

IMPORTANT!! All users executing Swisslog as administrator will lose this setting after upgrade. Remember to set it again in the Swisslog icon to avoid undesired issues.

Best 73]]> <![CDATA[Swisslog freezes if a non-valid locator is entered.]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1364 Wed, 24 Jun 2026 16:40:58 +0000 JW6VDA]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1364
Tom ex JW6VDA, now OH6VDA]]>
Tom ex JW6VDA, now OH6VDA]]> <![CDATA[new sequence ordering takes hours]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1363 Wed, 17 Jun 2026 07:08:34 +0000 DG7RO]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1363
when I delete some QSO in the database - here 8k QSOs - next time I start swisslog the new qso sequence number can be assigned.
This takes here hours: 10 QSOs per second!  Is there a possibility to speed up this?

Torsten, dg7ro]]>
when I delete some QSO in the database - here 8k QSOs - next time I start swisslog the new qso sequence number can be assigned.
This takes here hours: 10 QSOs per second!  Is there a possibility to speed up this?

Torsten, dg7ro]]> <![CDATA[Beta released on 5th July 2026]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1362 Wed, 17 Jun 2026 00:00:42 +0000 EA3GCV]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1362
I have released a beta including the following improvements (latest changes highlighted in boldface):
  • NEW: Optimized routines when processing Pendient Log QSO Requests. Raised queue limit to 3000 QSO.
  • NEW: Spanish DEE references: now Spanish DEE references has a 4 digit format (i.e EB-0001 instead of EB-001). Swisslog will automatically adapt old references to the new format at startup.
  • NEW: LLOTA references: now LLOTA references starts with LL (i.e. LLES-0001 instead of ES-0001). Swisslog will automatically adapt old references to the new format at startup.
  • Corrected: QSO Entry: Notes and Comments from the Callbook table were not saved if user switched into another tab before Saving the QSO.
  • Corrected: Update award information: International characters in reference names where not displayed properly.
  • Corrected: Logbook views > Update QSOs with data from Country Table and/or Callbook Cd / Internet databases: process halted if an Empty field was found
  • Corrected: QSO Entry: saving QSOs by means of the Save button added a small delay in the save procedure compared when pressing F10
  • Corrected: Double click actions on DX Windows / Band Maps: tuning and turning rotor actions were delayed a lot. Now both tuning/turning actions should be executed at the same time. If Log QSO it's one of the double click actions, it could take some seconds to be executed, depending the computer and user setup. This is a normal behaviour.
  • Improved:  Double click actions on DX Windows / Band Maps: actions should be executed slightly faster than in previous beta versions
  • Improved: DX Windows/Band Maps: improved algorithm to detect Spanish DEE references in spot comments. Sometimes POTA, TOTA or LLOTA references were confused as DEE because there are references which are exactly the same.
  • Improved: Flex Radio: when double clicking on  DX Windows / Band Maps, the frequency took seconds to be displayed in Swisslog. Now is faster.
  • Corrected: QSO entry: when entering a wrong QTH locator Swisslog freezes or continuous "QTH-Locator is invalid" error message are displayed.
  • Corrected: QSO Entry: sometimes pressing the Save button or pressing F10 the QSO was not saved and was needed to press again the Save button/F10 to complete.
  • Corrected: when a Swisslog update is available a dialog box with HMTL code is displayed

73]]>
I have released a beta including the following improvements (latest changes highlighted in boldface):
  • NEW: Optimized routines when processing Pendient Log QSO Requests. Raised queue limit to 3000 QSO.
  • NEW: Spanish DEE references: now Spanish DEE references has a 4 digit format (i.e EB-0001 instead of EB-001). Swisslog will automatically adapt old references to the new format at startup.
  • NEW: LLOTA references: now LLOTA references starts with LL (i.e. LLES-0001 instead of ES-0001). Swisslog will automatically adapt old references to the new format at startup.
  • Corrected: QSO Entry: Notes and Comments from the Callbook table were not saved if user switched into another tab before Saving the QSO.
  • Corrected: Update award information: International characters in reference names where not displayed properly.
  • Corrected: Logbook views > Update QSOs with data from Country Table and/or Callbook Cd / Internet databases: process halted if an Empty field was found
  • Corrected: QSO Entry: saving QSOs by means of the Save button added a small delay in the save procedure compared when pressing F10
  • Corrected: Double click actions on DX Windows / Band Maps: tuning and turning rotor actions were delayed a lot. Now both tuning/turning actions should be executed at the same time. If Log QSO it's one of the double click actions, it could take some seconds to be executed, depending the computer and user setup. This is a normal behaviour.
  • Improved:  Double click actions on DX Windows / Band Maps: actions should be executed slightly faster than in previous beta versions
  • Improved: DX Windows/Band Maps: improved algorithm to detect Spanish DEE references in spot comments. Sometimes POTA, TOTA or LLOTA references were confused as DEE because there are references which are exactly the same.
  • Improved: Flex Radio: when double clicking on  DX Windows / Band Maps, the frequency took seconds to be displayed in Swisslog. Now is faster.
  • Corrected: QSO entry: when entering a wrong QTH locator Swisslog freezes or continuous "QTH-Locator is invalid" error message are displayed.
  • Corrected: QSO Entry: sometimes pressing the Save button or pressing F10 the QSO was not saved and was needed to press again the Save button/F10 to complete.
  • Corrected: when a Swisslog update is available a dialog box with HMTL code is displayed

73]]> <![CDATA[New Country Table]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1361 Fri, 12 Jun 2026 21:53:50 +0000 EI4KF]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1361
In the update I reviewed and identified some of the UK callsigns where the licensee has elected to drop the regional identifier (GD, GI, GJ, GM etc). This is now allowable per a recent change from OFCOM.

The following definitions were added. It is by no means an exhaustive list, merely some of the most active stations.


M8TSH, M9SMC and M9WGP are all Northern Ireland, GI

M8DOI, M8HZR, M8IYV, M8LAO, M8NEG, M8SNT, M8UAT, M8XZA, M9DEL, M9SNW, M9SRU and M9STM are all Scotland, GM

M8CYE, M8ENA, M8FBB, M8PVZ, M8RBW, M9LPZ, M9MMB, M9MWZ, M9SAE and M9TGX are all Wales, GW


By far the vast majority of UK stations do wish to retain their country identity by sending the full prefix. However, should an accurate logbook be important, it is recommended that you review all UK calls worked and amend the DXCC where required.

If you encounter callsigns where Swisslog does not assign the correct DXCC, please post to this thread with the details.

73 de Erik EI4KF]]>
In the update I reviewed and identified some of the UK callsigns where the licensee has elected to drop the regional identifier (GD, GI, GJ, GM etc). This is now allowable per a recent change from OFCOM.

The following definitions were added. It is by no means an exhaustive list, merely some of the most active stations.


M8TSH, M9SMC and M9WGP are all Northern Ireland, GI

M8DOI, M8HZR, M8IYV, M8LAO, M8NEG, M8SNT, M8UAT, M8XZA, M9DEL, M9SNW, M9SRU and M9STM are all Scotland, GM

M8CYE, M8ENA, M8FBB, M8PVZ, M8RBW, M9LPZ, M9MMB, M9MWZ, M9SAE and M9TGX are all Wales, GW


By far the vast majority of UK stations do wish to retain their country identity by sending the full prefix. However, should an accurate logbook be important, it is recommended that you review all UK calls worked and amend the DXCC where required.

If you encounter callsigns where Swisslog does not assign the correct DXCC, please post to this thread with the details.

73 de Erik EI4KF]]> <![CDATA[NEW version 5.117]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1360 Fri, 12 Jun 2026 21:47:53 +0000 EA3GCV]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1360
I have just released version 5.117 implementing VERY IMPORTANT NEWS AND CORRECTIONS.

Please UPGRADE when asked and read the full list of corrections HERE. 

IMPORTANT!! All users executing Swisslog as administrator will lose this setting after upgrade. Remember to set it again in the Swisslog icon to avoid undesired issues.

Best 73]]>
I have just released version 5.117 implementing VERY IMPORTANT NEWS AND CORRECTIONS.

Please UPGRADE when asked and read the full list of corrections HERE. 

IMPORTANT!! All users executing Swisslog as administrator will lose this setting after upgrade. Remember to set it again in the Swisslog icon to avoid undesired issues.

Best 73]]> <![CDATA[NEW Trusted QSL 2.8.6]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1359 Thu, 04 Jun 2026 21:08:38 +0000 EA3GCV]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1359
A new version of Trusted QSL v2.8.6 has been released. List of corrections / news can be found here.

You can download it in the Download section of the website or by clicking here.

It's VERY IMPORTANT to upgrade to the latest TQSL version to avoid issues in the LoTW synchronization!

Best 73]]>
A new version of Trusted QSL v2.8.6 has been released. List of corrections / news can be found here.

You can download it in the Download section of the website or by clicking here.

It's VERY IMPORTANT to upgrade to the latest TQSL version to avoid issues in the LoTW synchronization!

Best 73]]> <![CDATA[Problems with 1 June Beta]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1358 Mon, 01 Jun 2026 14:03:06 +0000 EI4KF]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1358
If I click a callsign in JTDX, in this version the call comes to the Statistic Overview window but then disappears and reappears, which has always happened before quite quickly but now is with a delay. If I click on a callsign in a DX Messages window, there is a delay before the call comes to Statistic Overview. 

The launching of Swisslog in this version takes longer than normal.

Register of QSL Cards: the window opens but is not immediately populated.

Prior to posting this report I had rebooted the computer and compacted my database to rule out extraneous factors. I also reverted to the 29 May beta and do not see this issue in that version.

I have attached a zipped video that may help visualise some of the problem.

Erik.


.zip   SwisslV5_dDQmRbcLNh.zip (Size: 3,77 MB / Downloads: 1) ]]>
If I click a callsign in JTDX, in this version the call comes to the Statistic Overview window but then disappears and reappears, which has always happened before quite quickly but now is with a delay. If I click on a callsign in a DX Messages window, there is a delay before the call comes to Statistic Overview. 

The launching of Swisslog in this version takes longer than normal.

Register of QSL Cards: the window opens but is not immediately populated.

Prior to posting this report I had rebooted the computer and compacted my database to rule out extraneous factors. I also reverted to the 29 May beta and do not see this issue in that version.

I have attached a zipped video that may help visualise some of the problem.

Erik.


.zip   SwisslV5_dDQmRbcLNh.zip (Size: 3,77 MB / Downloads: 1) ]]> <![CDATA[Display Errors]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1356 Sat, 30 May 2026 09:25:20 +0000 dl6lbi]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1356 In the latest beta version, there are several bugs regarding the statistics display and in the "Remarks" window.

The statistics display changes when switching from the "Input" window, (Picture left) to the "Logbook" (Picture right) Please see the attached images: Fail.jpg (incorrect display) vs. the "Input" window (which is correct). This message appears only when some statistics fields are populated.

In the "Remarks" window, the font is too small and cannot be changed.

It would be nice if the date were fully displayed in the input window; currently, a digit is always missing.

73 de Ingo

.jpg   ok.jpg (Size: 288,63 KB / Downloads: 9)

.jpg   Fail.jpg (Size: 234,02 KB / Downloads: 6) ]]> In the latest beta version, there are several bugs regarding the statistics display and in the "Remarks" window.

The statistics display changes when switching from the "Input" window, (Picture left) to the "Logbook" (Picture right) Please see the attached images: Fail.jpg (incorrect display) vs. the "Input" window (which is correct). This message appears only when some statistics fields are populated.

In the "Remarks" window, the font is too small and cannot be changed.

It would be nice if the date were fully displayed in the input window; currently, a digit is always missing.

73 de Ingo

.jpg   ok.jpg (Size: 288,63 KB / Downloads: 9)

.jpg   Fail.jpg (Size: 234,02 KB / Downloads: 6) ]]> <![CDATA[New Country Table]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1351 Wed, 13 May 2026 13:11:34 +0000 EI4KF]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1351
Time difference corrections have been made for ZP Paraguay, UN regions Kazakhstan, JY Jordan.

A clean-up of callsigns has been made for KP4 Puerto Rico: deleted K4C, K4D, K4P and K4W. KB2YLE and KD2GQL have been added.

Definition updates are VJ2L = VK9L Lord Howe Is, WZ9K = KH8 American Samoa.


Swisslog will prompt to update soon.


73 de Erik EI4KF.]]>
Time difference corrections have been made for ZP Paraguay, UN regions Kazakhstan, JY Jordan.

A clean-up of callsigns has been made for KP4 Puerto Rico: deleted K4C, K4D, K4P and K4W. KB2YLE and KD2GQL have been added.

Definition updates are VJ2L = VK9L Lord Howe Is, WZ9K = KH8 American Samoa.


Swisslog will prompt to update soon.


73 de Erik EI4KF.]]> <![CDATA[Field Note in QSO window]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1350 Thu, 07 May 2026 11:37:09 +0000 OK1FBE]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1350 I have started to use the version 5.116 and have the following issue: When I try to edit the recorded QSO, the field Note is not copied int QSO entry window (Note is empty) and new text of note overwrites the old note after Save of record. In Logbook window is not possible to set Middleeuropean font (For Note field itwas possible in all previous  versions, only neccessary to set after each start of Swl). After installing the Beta this issue stays the same. I believe this was not an issue in version 5.115 and I will try to return to 5.115 version from backup, hopefully.
Best regards
Vaclav
OK1FBE]]> I have started to use the version 5.116 and have the following issue: When I try to edit the recorded QSO, the field Note is not copied int QSO entry window (Note is empty) and new text of note overwrites the old note after Save of record. In Logbook window is not possible to set Middleeuropean font (For Note field itwas possible in all previous  versions, only neccessary to set after each start of Swl). After installing the Beta this issue stays the same. I believe this was not an issue in version 5.115 and I will try to return to 5.115 version from backup, hopefully.
Best regards
Vaclav
OK1FBE]]> <![CDATA[Weird behaviour in QSO-Entry Field]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1349 Tue, 28 Apr 2026 07:13:11 +0000 oe3kab]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1349 I Type "Jordi" and in the field I read "idroJ".
It happens since I updaded to Vers. 5.116
HW?]]> I Type "Jordi" and in the field I read "idroJ".
It happens since I updaded to Vers. 5.116
HW?]]> <![CDATA[operator field]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1347 Fri, 17 Apr 2026 20:13:58 +0000 dk3uw]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1347
Any ideas ?

Martin 
DK3UW]]>
Any ideas ?

Martin 
DK3UW]]> <![CDATA[missing FT2]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1346 Fri, 17 Apr 2026 13:27:12 +0000 DL1IP]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1346
FYI, I've noticed these two things.

1. Export log to WSJT-X JTDX , Mode selection missing FT2
End 2.  Entry of QSOs      Membership Panel Rhein Ruhr DX Association
The problem always occurs on restart.

Otherwise, everything's great and thanks.
VY 73 DL1IP]]>
FYI, I've noticed these two things.

1. Export log to WSJT-X JTDX , Mode selection missing FT2
End 2.  Entry of QSOs      Membership Panel Rhein Ruhr DX Association
The problem always occurs on restart.

Otherwise, everything's great and thanks.
VY 73 DL1IP]]> <![CDATA[Feld Operator]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1345 Fri, 17 Apr 2026 09:47:37 +0000 dl6lbi]]> https://www.swisslogforwindows.com/forum/showthread.php?tid=1345
After the last update, the following error occurs: when entering text in the "Operator" field, the cursor always moves back one step to the beginning. This results in the name being written backwards in capital letters.
This is annoying because it requires a mouse click after the entered letters for the text to continue in the correct sequence in lowercase.

vy 73 de Ingo]]>
After the last update, the following error occurs: when entering text in the "Operator" field, the cursor always moves back one step to the beginning. This results in the name being written backwards in capital letters.
This is annoying because it requires a mouse click after the entered letters for the text to continue in the correct sequence in lowercase.

vy 73 de Ingo]]>