[DXBase] Call on QSO label solved!
Rick Glisson
[email protected]
Sun, 8 Jun 2003 18:16:52 -0400
Thanks everyone, especially Joe who called!. The problem was indeed that =
in the opcall field KF4YOQ was there. I had checked that field in the =
last 20 QSO's and it was N4XMX. That has been fixed. The mystery is how =
it got there since the date of all the affected QSO's were last year. =
There were several groups of around 30 QSO's that had the other =
callsign. They were not imported later, they were already in DXB2003 =
when the data was imported to DXB2004. These groups were not from any =
contest either. Haven't a clue but the problem has been fixed.
Thanks again!
-73 Rick N4XMX
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
The reason this message is shown is because the post was in HTML
or had an attachment. Attachments are not allowed. To learn how
to post in Plain-Text go to: http://www.expita.com/nomime.html ---