Paul added a very important piece of information: "There needs to be at least one (dummy) QSO in the log for the dupe checking to work."
On Mon, Mar 8, 2010 at 11:25 AM, Jim Reisert AD1C <[email protected]> wrote: > On Fri, Mar 5, 2010 at 5:53 PM, wo2n <[email protected]> wrote: > >> 1- What's the easiest way to find duplicate QSO's in your log, DX4win??? >> Doing house cleaning, hi.> > > I believe that DX4WIN considers a QSO a dupe if all of the following match: > > - call > - date > - time (not sure if exact or a time window) > - band > - mode > > In addition, if the County field is filled in for either QSO, that > must match also. > > So the easiest way would be to export your log in the highest DX4WIN# > format available (DX4WIN8) then import your .DXQ file into a new, > empty log in the same format. For the duplicate QSO import options, > choose "Imported QSO is ignored". > > In order to avoid losing all your group names, etc. do the following: > > - copy your .DXL file to a new name > - open that new .DXL file > - delete all QSOs using Multiple QSO Operation > - import the .DXQ file you made above > > 73 - Jim AD1C -- Jim Reisert AD1C, <[email protected]>, http://www.ad1c.us ______________________________________________________________ Dx4win mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
