[Dx4win] Oops

[David Kozinn, K2DBK]

Ok, this is entirely my own fault, I'm looking for a relatively easy way 
to fix this:

When 8.01 came out, I used the multi-qso functions to update frequency, 
name, and QTH. Prior to doing that, I did a backup of my DXL file so 
that I could fall back. Although I knew that there were some issues with 
parsing the comments (which have been fixed in 8.02), I did a cursory 
check through the converted log and everything looked fine. I started 
using the new file and made some more contacts, and all seemed well.

Yesterday I upgraded to 8.02 and decided to re-run the multi-qso 
functions again which worked fine. I did another spot check, but 
discovered what I'd missed the first time, which was that about 400 QSO 
records had basically gotten the entire contents of the "Notes for this 
call" put in there, so I wound up with a bunch of things like "Fred, 
near London" in the Name field.

I tried exporting just those fields (set a filter for "," in the name 
field) and exported those records using the DX4WIN 8 format, then tried 
to edit some of the records in the DXN file by hand as a test to see if 
I can manipulate things that way (I moved the QTH to where I thought the 
QTH field was) but when I re-imported (with "duplicate overwrites"), 
although the QTH field was correct, the Name field seemed to still 
contain all the information. (e.g., in the example above, it said "near 
London" in the QTH field, but still said "Fred, near London" in the Name 
field.

I guess ideally I'd like a relatively easy way to just move the Name 
field back to "Notes for this QSO", then let DX4WIN just re-parse that, 
but I couldn't find a way to do that where I didn't wind up with 
duplicate info. I may well have been doing something wrong, but I can't 
figure out what.

The worst case is that I'll go through the records manually and fix them 
(which is what I started doing), but I was wondering if anyone had any 
better suggestions?

-- 
73,
	David, K2DBK
	http://k2dbk.blogspot.com
	http://k2dbk.com
	twitter: @k2dbk