The only use for the making sure the mults are listed correctly in the log is
for calculating the pre log checking score. The best way to do this if you
made changes to your log is to rerun the log through TRLog. I created an
easier way to use Tree's READ function to do this. Start TRLog by typing TR
RESCORE. Sit back and watch (don't touch the keyboard until its done). Over
the next several minutes the calls and exchanges will be entered and "worked".
The rate meter is fun to watch! The result is a new LOG.DAT. The old LOG.DAT
is saved as PLOGxxxx.BAK.
You really only need to do the above work if you made changes to the log that
might effect mults or dupe status. Even then the only effect is to change the
score POST would CALCULATE and put in either the SUMMARY.DAT or LOG.CBR.
NONE OF THIS HAS ANY EFFECT ON YOUR REAL SCORE OR THE LOG CHECKING!
--
73 es God Bless de KK1L...ron rossi(kk1l@arrl.net) <><
Support Programmer for TRLog http://www.qth.com/tr
QTH: Jericho, Vermont
My page: http://www.qsl.net/kk1l
>In ARRL DX phone, I worked UT1FG/MM and later UX2IO - both on 15m. TR
>properly credited the /MM as no mult and the UX as a new mult "UR".
>
>Later, when I ran Post, it tried to give me credit for a "UR" mult on
>the call UT1FG/MM. When I said no, it then found UX2IO and said it was
>a duplicate multiplier even though at this point there was no valid UR
>in the log (/MM was NOT a "UR"). I again told it to ignore.
>
>To be sure, with modern log checking, multiplier flagging in the log is
>almost meaningless - just thought I'd point this out.
>
>73 Mike N2MG
>_______________________________________________
>Trlog mailing list
>Trlog@contesting.com
>http://lists.contesting.com/mailman/listinfo/trlog
|