[TRLog] Interesting Occurrence Using 6.59

[Bob Wanderer]

Yes CALLSIGN UPDATE ENABLE = TRUE
However, this occurred later in the contest when most
received serial numbers where two or more digits.

I won't swear this was the scenario each time the problem
occurred, but since I was S&P'ing, I would usually enter the
section, followed by the check, followed by the serial
number and precedence.  I recall using spaces, but that may
have been the problem for both being there or being left
out.  So a typical exchange window entry would look like
this:

LAX 88 43M

However, somethimes the problem occurred on one QSO but not
another yet I believe the data was inputed in the exact same
manner.

As previously mentioned, entering the callsign in the
exchange window (properly spaced) cured the problem so I
started to automatically enter it (a second time) prior to
contacting the station.  This would, however, be a concern
were I (successfully) running.

73
Bob AA0CY
-----Original Message-----
From: Richard Ferch [mailto:ve3iay@rac.ca]
Sent: Monday, November 26, 2001 10:05 PM
To: trlog@contesting.com
Cc: aa0cy@VRINTER.NET; VE7IN-Earl@shaw.ca
Subject: Re: [TRLog] Interesting Occurrence Using 6.59


Bob, Earl,

I'm guessing you have CALLSIGN UPDATE ENABLE = TRUE, right?
If so, whenever
the received serial number is a single digit, the SS
exchange with no spaces
looks like a possible callsign with the results you
described. The solution
is very simple: Always enter a space between the precedence
and the check in
the SS exchange. Alternatively, you can turn CALLSIGN UPDATE
ENABLE off, but
then you have to go through contortions whenever you copy
the callsign wrong
the first time around. Personally, I find it easier to hit
the space bar
unthinkingly after the precedence in every SS exchange. As
Udo pointed out,
this can happen in any contest where part of the exchange
can look like a
call sign - SS happens to be the worst culprit.

73,
Rich



--
FAQ on WWW:               http://www.contesting.com/FAQ/trlog
Submissions:              trlog@contesting.com
Administrative requests:  trlog-REQUEST@contesting.com
Problems:                 owner-trlog@contesting.com
Feature Wishlist:	  http://web.jzap.com/n6tr/trwish.html