Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Error on Swisslog 5.91
07-01-2016, 08:36 PM, (This post was last modified: 07-01-2016, 08:50 PM by EA3GCV.)
#6
RE: Error on Swisslog 5.91
Hi,

I reply you in English so that everybody can read it ;-)

I have improved this function in next version 5.91a. Now it will run about 25-30% faster and user will be able to see exactly which QSOs have been corrected and even save it to a text file. If all goes well I will release this version next week. Stay tuned and perform again this operation. It's advisable to perform a second time this function because maybe some QSO are corrected again. In this case you will have to manually edit every QSO and change the partner QTH-Name to allow different DXCC allocations for the same station. QTH-Name field is used to set a name for the same station worked many times from different locations or award references (DXCC, IOTA, SOTA, DCE, etc). Let me show you a real example:

- I worked 4L4HMC on 07/05/1992 and on 19/08/1992. Swisslog set 4L in both cases then assigned the same QTH-Name for both QSO (HomeQTH). After performing the first time the "Set DXCC from CLublog" the QSO on 07/05/1992 was corrected to UAEU (European Russia) while second QSO on 19/08/1992 is 4L (Georgia). What happens? this function corrects DXCC and sets UAEU to the first QSO.  But because when I entered the QSO Swisslog assigned 4L to both (then using the same QTH-Name: HomeQTH) automatically Swisslog use UAEU in the same QTH-Name for all other QSO having the same QTH-Name. QSO on 19/08/1992 must be set to 4L and change the QTH-Name to avoid "conflict" with first QTH. Second time you perform this operation will detect that the second QSO it's not well allocated (reads UAEU where really is 4L) and corrects it. But, again, because first QSO is using the same QTH-Name it changes 4L to both QSO which is not correct. We are in a kind of loop everytime you run this function and nothing is really corrected.

I haven't found an automatic way to change the QTH-Name in these cases. That's the reason I have improved this function to keep a list of QSO corrected so that user can manually modify and correct this behaviour. You won't find many QSOs matching this situation but the solution is simple: edit each of these QSO, set the right DXCC and assign a different QTH-Name. In the above example I set HomeQTH for the first QSO (UAEU) en 4L for the second QSO.

I hope you understand what I mean. That's why Swisslog keeps different QTH-Name in QSOs with the same callsign but working in different locations. Swisslog does it automatically when entering in real time. If I find a way to correct this behaviour in future versions I will do it but I think this is the best solution up to now. The part of code to detect all this is extremely complicated. I should remind everybody that I'm not Walter, the author of this software and I find many difficulties to implement many things. However if I find a way I will implement it in future versions.

Best 73
Jordi, EA3GCV
Current developer of Swisslog
Reply


Messages In This Thread
Error on Swisslog 5.91 - by EA1FFO - 06-01-2016, 05:20 PM
RE: Error on Swisslog 5.91 - by EA3GCV - 06-01-2016, 06:07 PM
RE: Error on Swisslog 5.91 - by EA1FFO - 06-01-2016, 09:23 PM
RE: Error on Swisslog 5.91 - by EA1FFO - 07-01-2016, 10:08 AM
RE: Error on Swisslog 5.91 - by EA1FFO - 07-01-2016, 05:11 PM
RE: Error on Swisslog 5.91 - by EA3GCV - 07-01-2016, 08:36 PM
RE: Error on Swisslog 5.91 - by EA1FFO - 07-01-2016, 10:10 PM
RE: Error on Swisslog 5.91 - by EA3GCV - 08-01-2016, 12:56 AM
RE: Error on Swisslog 5.91 - by EA3GCV - 09-01-2016, 06:55 PM
RE: Error on Swisslog 5.91 - by EA1FFO - 12-01-2016, 04:51 PM
RE: Error on Swisslog 5.91 - by EA1FFO - 12-01-2016, 04:57 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)