Swisslog, WSJT-X and JTAlert

[EA3GCV]

Hi Tom,

I understand what you mean. But I have to keep a logic and consistence of how Swisslog is designed. All info regarding the callsign, QTH etc used in the QSO is set in MyQTH table. You associate a MyQTH (the same as a Working Condition and Event) to every QSO. So the right place to add the Operator Callsing is in the MyQTH details. In this way will be in 5.98c. When you import QSOs you have to select the MyQTH, working conditions and Event to be assigned to every imported QSO. It's a very good way to keep all your QSOs classified and ready to handle in logbook views, export, statistic etc. Because you can get a statistic report for a certain MyQTH. You only have to create a MYQTH for every operator only once. It's very easy to select the MYQTH when this operator works from the club station. Maybe you won't like but it's the way Swisslog works and it offers the most flexible option to fit all user needs (clubs, multioperator and single stations). It's a different way compared to N1MM but in Swisslog I the only and logical place to add this field is in the MyQTH settings. After creating a MyQTH for every operator, it's really simple to select the MyQTH to work QSOs and you have all control to even know DXCC statistics for every operator. You won't find this feature in other logging program the same way as Swisslog handle all this thanks to the relation between the Logbook table (QSO data) and the MyQTH table.

Regarding dupes, when you import data into Swisslog, dupes are handled in the selected MyQTH. Dupes means the exact date, time, band and mode. So no worry about finding a dupe even if the same QSO has been worked by other operator at the same time because it's assigned to a different MyQTH. 

Best 73