Bill I think this may be the problem. DXB still thinks that the PARTICULAR qso entered has the old prefix assigned to it. take your example 4U/F6IRF YK XU if you do a search on the call field for that particular qso you will find that in the Prefix field it still lists this qso as for Syria (YK) Go to that prefix field and change the prefix to indicate the XU (Cambodia) and hit F10. You will get a pop up asking if you want to record this qso as being with XU. Say yes.
You will have to do this with each of the problem qso's. DXB has a large db of "calls used to be", "calls that even though they indicate this" etc. but obviously they don't have every one. I found that most of mine where the old ones. Guess that's the price us old farts must pay for worked stations during the old spark gap days. :-) You might send those old ones to Jack and he may include them in his alias database for future inclusion into DXB. ------------------------------------------------------------ "The computing field is always in need of new cliches. ------------------------------------------------------------ Bill H. in Chicagoland [EMAIL PROTECTED] ----- Original Message ----- From: "William Hein, AA6TT" <[EMAIL PROTECTED]> To: <[email protected]> Cc: <[EMAIL PROTECTED]> Sent: Friday, January 11, 2002 1:46 PM Subject: [DXBase] DXCC Prefix Callsign Mapping Problem > I switched from LOGPlus 3.55b to DXBase 2002 v1.01 a few months ago. It has been a lot of work transferring 75,000 QSOs from one program to another! One persist problem is that my DXCC totals (including band countries and related totals) are ALL lower on DXBase reports even though I have meticulously tracked all of the 'problem' prefixes over the years and carefully entered this data into DX Base: 3D2, 4U, KC6, VP8, ZK1, et al. > > I have made about 100 entries in the DXBase Prefix Callsign Mapping Table, assigning the correct DXCC Prefix to each callsign according the QSL card and other information known to be correct. However, DX Base continues to count these QSOs under their old, default DXCC Prefixes apparently without regard to the data in the Prefix Callsign Mapping Table. > > It does not matter how many times I run Initialize Tables, the old -- incorrect -- DXCC Prefix data is still associated with these QSOs. A few examples: > > CALL DXBASE DEFAULT PREFIX CORRECT PREFIX > > 4U/F6IRF YK XU > 4U/N6BFM YK YI > 4U/T93A YK HH > KA2AM K JA > KA2GS K JA > TO2T F FG > VI0ANT VK KC4 > VP8CBE VP8 VP8H > VP8CKC VP8 VP8O > VP8SGP VP8 VP8G > ZK1UVO ZK1/S ZK1/N > ZK1VDX ZK1/S ZK1/N > ZK1VTK ZK1/S ZK1/N > ZX0A PY0F KC4 > etc... > > Curiously, if I enter a new QSO into DX Base with any of above callsigns the DXCC Prefix information seems to be correct on this new test QSO. However, the old QSOs under such callsigns cataloged in DX Base continue to have the old, incorrect DXCC Prefix data. > > Help! What am I doing wrong? I have read the DX Base Help file backwards and forwards on this topic. > > Bill AA6TT > Topsham VT > > ------------------------------ > William H. Hein, AA6TT > 10 Clark Road > Topsham VT 05076-3086 USA > tel 802/584-4317 > ------------------------------- > http://www.AA6TT.com > email [EMAIL PROTECTED] > MSN IM [EMAIL PROTECTED] > ------------------------------- > _______________________________________________ > DXBase Reflector - Please visit us on the web at www.dxbase.com > - - - - - - - - - - - - - - - - - - - - - - - > To UNSUBSCRIBE please visit: > http://mailman.qth.net/mailman/listinfo/dxbase > >
