[Dxbase] Lessons Learned from the 4O modifications -- Joe WA6AXE

Fri May 25 10:07:25 EDT 2007

Just a quick note to say that Joe's additional instructions work just fine
for those of us that have a few of the previous YU6 prefixes in the log. I
believe this additional step is only required for those who have logged
stations from Montenegro after the end of June 2006(?).
On and ending thought, from experience, it can not be stress enough that you
must make a copy of both your logbook data and the refdata before starting.
Joe's instructions are accurate and easy to follow, but no matter how
confident you are on a keyboard it only takes one outside distraction to
mess up an entry. 
Thanks to everyone,
Eric.
> -----Original Message-----
> From: Joseph Glockner
>> TO all:
>> If you go through the step-by-step instructions and end up 
> "trying" to "change" your YU6 PFX QSO's to the new 4O - and 
> you end up with an error that says something about " 
> Numerical Stats.... etc " .. nothing is lost at all ..
>> Go back into the Country Prefixes database and under the 
> Primary TAB, ADD back at the bottom of the database listing 
> the YU6 again -- BUT - this time in the DXCC column use the 
> DUUMMY DXCC # of 516 ...
>> Once you have the YU6 entry installed again ONLY in the
> Primary TAB is needed -- close out that window and go
> to your Previous QSO window -- and "this time" you will see
> that when you FIND the YU6 Prefix, your YU6 QSO's will
> be there "WITH" the Prefix column showing YU6 -- vice
> the BLANK (nothing in that column) that was noted before -
> and causing the error...
>> OK - once you update ALL of your YU6 qso's to 4O in the 
> Prefix column of all the qso's --- do a FIND again for YU6 
> Prefix -- this time - NONE should show up at all ... if this 
> is the case, close out the Previous QSO window and go back 
> into the Country Prefixes database (Primary TAB), and DELETE 
> the YU6 entry from that TAB completely ... your 4O will 
> remain in that Primary TAB ...
>>> You are ALL OK now -- and you should be able to initialize 
> stats and show HF Numeric Stats,, etc etc all ok ...
>>> I have a guess as to why this is happening - but, suffice to 
> say that if you run into this error -- you can get everything 
> back to NORMAL again within minutes....