LOTW import has messed up log

[EI2GLB]

Hi All

I imported my QSL file from LOTW and it has messed up my log,

Of course I hadn't done a back up before hand so am I now in trouble,

when I went to upload it i got 1600+ errors from clublog which is the same number as credits from LOTW

anyone any ideas how I can removed the corrupted LOTW QSO's from my log,

Thanks
Trevor

[K7PT]

Trevor,
The only thing Log4OM changes when you do the LOTW download is to change to QSL status to "V" (Verified). So, I don't understand what you mean by "corrupted". Please a few details or send me the QSOs via my private mail (k7pt at k7pt.com).
Thanks.

[EI2GLB]

Hi Chuck

The 1600 odd qso's from lotw none of them had any times and when merged into my log created dupes that clublog picked up on, when I tried to start HRD label it caused my PC to crash trying to send 1600 error reports,

I'm not near the PC at present but I'll send them soon

Thanks
Trevor
EI2GLB

[K7PT]

OK, those must have been very old Qs that came from cards if they had no times. So, Log4OM created a qso for them.

These should have been done manually as Log4OM looks for an exact match in your log. With no match for those, it created what you call "dups".

In my opinion it should display an exception list and let you decide which QSO.

[IW3HMH]

No time means 00:00 be assigned as default, because time is a key.
Log4Om cannot decide that a QSO with no time is not valid or dupe in your log, as you can have multiple qso with the same callsign in the same day...