Entry of QSOs - /P SOTAs with different QTH/Locators field

[EA3GCV]

Hello,

Swisslog keeps the field HOMEQTH the same way for the MYQTH: a new profile must be created for a new location of the QSO partner if it's the same callsign. For regular stations the default name is HOMEQTH. If working a portable station it will be /P, mobile stations /M etc. Swisslog handles this automatically. Let's see an example:

- First QSO with EA3GCV/P on SOTA EA3/BC-001. Swislsog will create the /P HomeQTH
- Second QSO with EA3GCV/P on SOTA EA3/BC-002. Because it's the same callsign but it's in another location (another SOTA) the proposed HomeQTH will be the SOTA reference EA3/BC-002.

By default Swisslog warns user that a new HomeQTH must be added for the QSO partner informing the proposed name in case user wants to change it. Really there is no reason to change it because Swisslog assigns a name according the reference changed from the latest location. So, the answer must always be YES unless you want to assign another name. If you reply NO you will overwrite the location info in all previous QSO with this station! So in this example you will assign EA3/BC-002 to the previous QSO which is wrong. You can disable this warning in the Options of the QSO Entry window (Issue warning if a new QTH is needed). I suggest to do this.

Once you know the reason of all this, now let's go to this issue. I have received very very few similar reports from users experiencing this strange issue. All of them have in common that they are using Windows 7. There are users using Windows 7 not having this issue at all but according to my experience it's something related to W7. Under Window 10 this don't happen.

So if you are using Windows 7 the only solution is to upgrade to Windows 10. Don't hesitate to do this, not only for Swisslog but Windows 10 it's faster, more secured and stable that any other previous version. You can upgrade directly into Windows 10 from Windows 7without losing anything. Maybe you will have to upgrade to the latest version of some programs and, of course, upgrade drivers but it should work perfectly. I know deeply all Windows OS since Windows 3.1 and believe me, you need to upgrade to W10.

In case you have Windows 10:

- Add an exception to Swisslog in your antivirus, firewall and any antimalware software. THIS IS VERY IMPORTANT!
- Make sure you have latest Windows version. Now it's 20H2 released on november. Check Windows updates.
- Try forcing Swisslog to run as administrator (mouse right click on the Swisslog icon, Properties > Compatibility > Run as administrator checkbox).

Let me know something.


Best 73