I wish I could help you, Dick. I have the same problem. Most of the
35K QSOs in my DX4Win database are imports from CT, TR and Writelog
contest logs. For CT and TR I use logconvert to convert to ADIF. For
Writelog I used its own ADIF generation function. Then I import the
ADIF using DX4W.  Most of the resulting records have loads of
extraneous info in the Notes for This Call field. Much of it never
appeared in any field of the original logs. It must be coming from
some kind of global database that DX4Win sucks in without provocation.
I've asked before on this reflector but never received a coherent
response. Since all I use DX4Win for is replying to received QSLs, it
works for me. But it seems to be useless as a general logger because
of all this random garbage it keeps jamming in that field. I wanted to
use it as my daily logger but I've fallen back to Writelog for that.

73,

/Rick N6XI

On 5/9/05, Dick Flanagan <[EMAIL PROTECTED]> wrote:
> DX4WIN 6.04:
> 
> I have recently noted that some of my Notes For This Call fields are being
> modified without any input from me.
> 
> For example, on one QSO I put the Op's name in the field and somehow "Juan"
> has now become "Juan/Juan."
> 
> If that isn't interesting enough, I have three QSOs from one particular
> station where the Notes For This Call field now contains
> "Yul/Yul/Yul/Yul."  (I guarantee you that I only entered the first Yul.)
> 
> Some DX4WIN operation is causing this and I would like to locate it before
> these fields start to look really ugly.
> 
> Any ideas?
> 
> 73, Dick
> --
> Dick Flanagan K7VC NV SM
> E-mail: [EMAIL PROTECTED]
> 
> _______________________________________________
> Dx4win mailing list
> [email protected]
> http://mailman.qth.net/mailman/listinfo/dx4win
> 


-- 

Rick Tavan N6XI
PO Box 10270
Truckee, CA  96162-0270
530 587 3164 Truckee
408 896 0476 Cell
408 867 5797 Saratoga
650 846 5214 Voice Mail
From [EMAIL PROTECTED]  Sat May 14 17:08:17 2005
From: [EMAIL PROTECTED] (Jim Reisert AD1C)
Date: Sat May 14 17:17:01 2005
Subject: [Dx4win] Notes For This Call Oddities
In-Reply-To: 6667
Message-ID: <[EMAIL PROTECTED]>

--- Rick Tavan N6XI <[EMAIL PROTECTED]> wrote:

> I wish I could help you, Dick. I have the same problem. Most of the
> 35K QSOs in my DX4Win database are imports from CT, TR and Writelog
> contest logs. For CT and TR I use logconvert to convert to ADIF. For
> Writelog I used its own ADIF generation function. Then I import the
> ADIF using DX4W.  Most of the resulting records have loads of
> extraneous info in the Notes for This Call field. Much of it never
> appeared in any field of the original logs. It must be coming from
> some kind of global database that DX4Win sucks in without provocation.

DX4WIN does not have any such "global database".

Note for this Call append if there is additional/new information in the log you
are importing.  For example, if your log has "Jim" listed under AD1C, and the
ADIF file to be imported has "JIM" in the notes field, then the resulting
DX4WIN note will look like:

  Jim | JIM

I can assure you that if you had used C2A (CT to ADIF) from the K1EA web site,
the notes would have remained unchanged, since it doesn't write to any notes or
comment field (except if you ask for special treatment, like SS exchange,
etc.).

My suspicion is that LogConvert is creating these notes.  Have you ever looked
at the ADIF file to see what's in it before you imported it?

If you can give me a sample .DXL and .ADI file that demonstrates a problem, I
would be happy to work with you to help you understand/resolve it.  

73 - Jim AD1C


--
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.us
From [EMAIL PROTECTED]  Sat May 14 17:48:17 2005
From: [EMAIL PROTECTED] (Alan Zack)
Date: Sat May 14 17:57:02 2005
Subject: [Dx4win] Deleting QSO's
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

Thanks Cesar,
That did it except since all the incorrect QSO's were in one Group 
Number I used the Group Number instead of date range in the 
PREFERENCES.  But I had not figured out that I needed to use the 
PREFERENCES to select the QSO's to be deleted until you pointed it out 
so that info really helped.  I held my breath until the message popped 
up, "You are about to delete 1243 QSO's".  Since this figure exactly 
matched the entries in the CT Contest log I knew I was OK.
I use the little USB memory sticks for back up saves.  I saved the 
virgin log onto two of these just to be safe!
Thanks again (P.S. I am in your many DXpedition and Contest logs as 
K6ACZ before I moved here).
73

PY2YP wrote:

> Hi Alan,
> 
> Please do as follow:
> 
> 1. Do a backup copying the .DXL file into a disk;
> 2. Use F8 to select the Qs;
> 2.1. Be sure to have QSO DATE = RANGE in the PREFERENCES | QSO tab
> 3. Then go to QSO | MULTIPLE QSOS OPERATIONS | DELETE QSOS
> 
> That's it.
> 
> 73 DX de PY2YP - Cesar
> ----- Original Message ----- From: "Alan Zack" <[EMAIL PROTECTED]>
> To: <[email protected]>
> Sent: Wednesday, May 11, 2005 9:35 PM
> Subject: [Dx4win] Deleting QSO's
> 
> 
>> I keep two separate DX4WIN Logs, one for my home QTH contacts and 
>> another for my portable DU operations.
>> I just discovered I accidentally transferred a CT based ARRL 10 meter 
>> DX contest log into my home QTH log instead of the portable DU log 
>> where it belonged.
>> When I did the download I assigned this contest log its own DX4WIN 
>> Group number and all the contacts are within a 48 hour time frame.
>> Is there an easy way to delete this group of contacts completely from 
>> my log or must I delete these Q's one at a time?
>> The contacts are now in the DU log where they belong but I want to rid 
>> the Home Log of these contacts to avoid confusion with my DXCC, WAZ, 
>> etc, tracking.
>> TIA
>> -- 


-- 
__________________________________________________________________________ 

Alan Zack
Amateur Radio Station K7ACZ
Las Vegas, Nevada, USA
Quality Engineer, The Boeing Company, Retired
Aviation Chief Warrant Officer, U.S. Coast Guard, Retired
U.S. Coast Guard, Always Ready, Always There
Every hour, Every day, Around the Clock and Around the World
SEMPER PARATUS
http://www.gocoastguard.com
DEPARTMENT OF HOMELAND SECURITY

Reply via email to