Greg, You're right. It should have selected KC4 and not KG4. This is an error in our alias prefix logic. We've made a note to correct this in the future, but meanwhile, you can overcome the issue by adding a full callsign map for KC4/N2TA and map to KC4.
Thanks for pointing this out. Regards, Jack ----- Original Message ----- From: "Greg - N4CC" <[EMAIL PROTECTED]> To: <dxbase@mailman.qth.net> Sent: Friday, November 29, 2002 6:45 AM Subject: [DXBase] Mapping > Jack -- question on mapping -- I worked KC4/N2TA this morning and noticed > that when I tabbed over, the prefix came up as KG4 rather than KC4...(not a > problem...easily fixed) but I figured it was just an error in the prefix > mapping data base somewhere and I would fix it...but I can't find anywhere > that maps the prefix KC4 to KG4. Why would this come up as KG4? 73 de Greg > _______________________________________________ > DXBase Reflector - Please visit us on the web at www.dxbase.com > - - - - - - - - - - - - - - - - - - - - - - - > To UNSUBSCRIBE please visit: > http://mailman.qth.net/mailman/listinfo/dxbase >
