[Dxbase] PJs

[Glenn Lowery]

It would be interesting to see the results of the following concerning K4YR's 
situation:

Copy the QSO data for say the single PJ4I contact on a sticky, then delete that 
one QSO record all together itself, then RELOAD the exact same QSO data and see 
what the program "auto recognizes" the entity to be.

I myself have not run the updater...but, I'm getting ready to.  Mine will be 
somewhat different, since I have NOT loaded any QSOs into DXbase 2007 since 8 
October.  Everything I worked after 8 October was manually listed elsewhere 
while awaiting the updater.  Yes, it's quite a lot of Q's, but, I also wanted to 
give Neal and the beta testers time to work out all the bugs.

After I run the updater (over the coming weekend) and start loading in all the 
new PJs and other contacts, I'll be able to report any misidentifications 
immediately upon hitting tab after each callsign.  And this method is no 
longer/time comsumin than any other, since we all had to "type" in the QSO 
records at some point :-)

73 - Glenn, K2FF




________________________________
From: Pat Parrish <k4yr at skybest.com>
To: Dxbase at mailman.qth.net
Sent: Mon, December 13, 2010 6:45:18 PM
Subject: [Dxbase] PJs

Neal
I logged something over 75 new PJs for bands/modes.  The Updater failed to 
correctly assign correct status to 4 PJ2Ts, 1 PJ2/W5MPC and 1 PJ4I.  All other 
Qs with each call & all others are correctly recognized.  I have been unable to 
see any logged differences in the 6 noted.  It's been so long since I manually 
corrected DXCC status with DXBase 2007 log that I've forgotten the procedure and 
have been unable to do so manually.  Any help, please?  Thanks
K4YR
______________________________________________________________
Dxbase mailing list
Home: http://mailman.qth.net/mailman/listinfo/dxbase
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Dxbase at mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html