I am curious what people do with a log entries that are not QSLable? I have a couple that either the call does not match a valid ham or some other issue that prevents me from any hope of a qsl. I don't want to keep thinking I worked Madagascar 5S5. But I would hate to delete the entry from the log, and find out that dyslexia caused me to miss slovenia S5.
I was changing the log entries for these QSO's to report a K as the entity, but I was wondering if there was a better way. Bob - N6RI From [EMAIL PROTECTED] Thu Mar 9 18:17:34 2006 From: [EMAIL PROTECTED] (FireBrick) Date: Thu Mar 9 18:19:19 2006 Subject: [Dxbase] No QSL Message-ID: <[EMAIL PROTECTED]> Go to the Valid Column, and untick both. It will now remain in you log, but not be counted in your stats. And if a future cluster spot should appear, it will report it as unworked/unconfirmed. And if some day a card appears from the burea with which explains a busted call, you can just mark it as such and retick those Valid entries. On 3/9/2006 4:54:34 PM, Robert Tortajada ([EMAIL PROTECTED]) wrote: > I am curious what people do with a log entries that are not QSLable? I > have a couple that either the call does not match a valid ham or some > other issue that prevents me from any hope of a qsl. I > don't want to > keep thinking I worked Madagascar 5S5. But I would hate to delete the > entry from the log, and find out that dyslexia caused me to miss > slovenia S5. > > I was changing the log entries for these QSO's > to report a K as the > entity, but I was wondering if there was a better way. > > Bob - N6RI > ______________________________________________________________ > Dxbase mailing list > Home: http://mailman.qth.net/mailman/listinfo/dxbase > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[email protected]
