[Dx4win] Help importing old version log to 9.09

[Brian McGinness]

Ok your going to laugh me out of the house here, but I am using dx4win
version 1.12 (under windows 10 x86 no less) and finally want to upgrade to
the latest version. I'm probably the only one, LOL. Had to stay with 32-bit
windows 10 so it would run the 16-bit very old version.

Been playing with 9.09 in the demo mode.

I'm finding a bug in the import process concerning the CW mode.

The export from 1.12 looks fine and everything seems to import fine to 9.09
except CW QSOs. They come in as either SSB or FT8 QSOs, and there is an
error in the notes field saying {Mode=CW } for every CW QSO in the log.

I don't want to use adif because I want to try to keep the dx4win specific
dxcc and vucc tallys, which are importing correctly.

I'm guessing there is some kind of parsing error with CW because it is only
two characters (and a space), where the other modes in the log all use
three characters (FSK and PHO).

I even tried adjusting the text file from _CW to CW_ and it didn't change
anything.

I can filter the new log by the error in the notes and just get the QSOs
that need fixing.

Is there any way to bulk update a field for all QSOs in a filter view?

If not, am I doing something wrong or is there a bug importing logs from
very old versions? The filter list says it will, but it won't. It can't
correctly interpret a CW qso even though the file plainly shows CW as the
mode.

I even tried making my own filter using a text export/import with exactly
the same results.

Maybe I could export the bad QSOs with a filter view, fix them outside of
dx4win, then import them back in overwriting the old QSO (hopefully) but I
can't verify this will work since the demo version won't export
(understandably).

I don't want to purchase till I verify I can successfully move my log over.

Or I can manually fix 2600 QSOs but will take up a lot of time.

Any ideas?

Thanks

Brian N3OC