Does this happen with EVERY qso or just a few?

That qso is already entered into the log.
You trying to enter a qso that is an exact match for an pre-existing qso.

The fellow I manage does this occasionally.
He exports a section of his log and accidentally overlaps with the previous
section he sent.

Or your trying to enter the log a second time.



----- Original Message ----- 
From: "Paul Wyse" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Sunday, June 08, 2003 5:36 PM
Subject: [DXBase] Merging logs


> My QSL manager sends me an ADIF file (sample below) with the
> QSL information which I would like to update my log.  When I
> import the file, I get the ERROR message at the bottom of
> this message.  How can I incorporate his QSL information.  A
> number of stations have QSL'd to me so there is information
> in my log that are not in the QSL managers.  Any
> suggestions?  I have recently upgraded from DXB 2002 to DXB
> 2004.  I tried importing the data (*.adi) from my QSL
> manager to my ET3PMW.mdb and get the error message below.  I
> don't find any information in the help file re: merging
> infomation.
> 73,
> Paul W4PFM/ET3PMW
>
> <CALL:6>OK1FDB<PFX:3>OK1<QSO_DATE:8>20020212<TIME_ON:4>1940<
> BAND:3>15M<MODE:3>SSB<FREQ:8>21.00000<NAME:8>Jaroslav<QTH:15
> >CZ-27200
> Kladno<DXCC:3>503<CONT:2>EU<CQZ:2>15<ITUZ:2>28<RST_RCVD:2>59
> <RST_SENT:2>59<TX_PWR:3>100<QSL_SENT:1>N<QSL_RCVD:1>N<EOR>
>
> ERROR:  OK1FDB The changes you requested to the table were
> not successful because they would create duplicate values in
> the index, primary key, or relationship.  Change the data in
> the field or fields that contain duplicate data, remove the
> index, or redefine the index to permit duplicate entries and
> try again.   OK1FDB   20020212   1940   21000.00   15m
> USB   59   59
>
> _______________________________________________
> DXBase Reflector - Please visit us on the web at www.dxbase.com
> - - - - - - - - - - - - - - - - - - - - - - -
> To UNSUBSCRIBE please visit:
> http://mailman.qth.net/mailman/listinfo/dxbase
>
>

Reply via email to