Error Import Adif File from Radioges

[ea4t]

Good night to everyone, I introduce myself.
I am a new user of this program. My name is Jorge Gallardo, EA4T, and I live in Madrid, Spain.

I use Radioges by friend Antonio EA4YG.
But as it is very old, and does not update the program, I have seen myself in the need to find another.
And they recommended this.

Apart from the configuration and having to study the operation of the program a bit, I created several databases.
For each of my indicative.

With my previous indicative of EA4AYW, I am having problems when importing the file that generated the Radioges in Adif format to the log4om.
The file consists of 34284 records, but I care only 34062 records.
In the import I have seen that the result of importation with Save Log can be saved, and that generates a Txt file, with the result.
I see where the mistakes are, but I do not understand what is the problem of error.
I put some examples of the errors, so that you indicate where the error can be.

WARNING: Callsign: EA4URQ Date: 01/01/0001 0:00:00 Band: 40m Mode: LSB QSO NOT VALID. SKIPPING IMPORT
WARNING: Callsign: EA5GOR Date: 01/01/0001 0:00:00 Band: 40m Mode: LSB QSO NOT VALID. SKIPPING IMPORT
WARNING: Callsign: EA2EEK/P Date: 01/01/0001 0:00:00 Band: 40m Mode: LSB QSO NOT VALID. SKIPPING IMPORT
WARNING: Callsign: EA5XY Date: 01/01/0001 0:00:00 Band: 40m Mode: LSB QSO NOT VALID. SKIPPING IMPORT
WARNING: Callsign: EA6AIU/P Date: 01/01/0001 0:00:00 Band: 40m Mode: LSB QSO NOT VALID. SKIPPING IMPORT
WARNING: Callsign: EA5RKX Date: 01/01/0001 0:00:00 Band: 40m Mode: LSB QSO NOT VALID. SKIPPING IMPORT
WARNING: Callsign: EA4SE Date: 01/01/0001 0:00:00 Band: 40m Mode: LSB QSO NOT VALID. SKIPPING IMPORT
WARNING: Callsign: EA3HWD Date: 01/01/0001 0:00:00 Band: 40m Mode: LSB QSO NOT VALID. SKIPPING IMPORT
WARNING: Callsign: EA5ES/P Date: 01/01/0001 0:00:00 Band: 40m Mode: LSB QSO NOT VALID. SKIPPING IMPORT
WARNING: Callsign: EA7URI/P Date: 01/01/0001 0:00:00 Band: 40m Mode: USB QSO NOT VALID. SKIPPING IMPORT
WARNING: Callsign: EA7EPF/P Date: 01/01/0001 0:00:00 Band: 40m Mode: LSB QSO NOT VALID. SKIPPING IMPORT
WARNING: Callsign: EA3HUX Date: 01/01/0001 0:00:00 Band: 40m Mode: USB QSO NOT VALID. SKIPPING IMPORT

I see this type of error, and although the date puts 01/01/0001 and 0:00:00, in the Adif file, generated by Radioges, there is no that time or those dates.
From what I understand that it must be the log4om who did not know how to interpret it, or put it that way for some other error.

constraint failed UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode Callsign: EA5CAZ/P Date: 04/04/1999 9:55:00 Mode: SSB Band: 2m
constraint failed UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode Callsign: EA5BK Date: 14/10/2004 21:49:00 Mode: SSB Band: 80m
constraint failed UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode Callsign: EA5GQK Date: 15/10/2004 21:42:00 Mode: SSB Band: 80m
constraint failed UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode Callsign: EA5FHK Date: 15/10/2004 21:42:00 Mode: SSB Band: 80m
constraint failed UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode Callsign: ED4URH Date: 23/04/2005 21:06:00 Mode: SSB Band: 80m
constraint failed UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode Callsign: EA7SK Date: 23/05/2005 21:24:00 Mode: SSB Band: 80m
constraint failed UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode Callsign: EA4TF Date: 02/07/2005 14:32:00 Mode: SSB Band: 2m
constraint failed UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode Callsign: ED3MCF Date: 13/03/2006 22:18:00 Mode: SSB Band: 80m
constraint failed UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode Callsign: EA5GQK Date: 13/11/2006 22:43:00 Mode: SSB Band: 80m
constraint failed UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode Callsign: EA5FHK Date: 13/11/2006 22:43:00 Mode: SSB Band: 80m
constraint failed UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode Callsign: EA5ASU Date: 14/11/2006 22:58:00 Mode: SSB Band: 80m
constraint failed UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode Callsign: EA5GRC Date: 14/11/2006 22:58:00 Mode: SSB Band: 80m
constraint failed UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode Callsign: EA5URM Date: 25/04/2007 20:45:00 Mode: SSB Band: 80m
constraint failed UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode Callsign: EA7FQS Date: 16/05/2007 21:32:00 Mode: SSB Band: 80m
constraint failed UNIQUE constraint failed: Log.qsodate, Log.callsign, Log.band, Log.mode Callsign: EA5ASU Date: 16/05/2007 21:34:00 Mode: SSB Band: 80m


They are different failures, or refer to the same error.
As I interpret where or what is the failure.
I have searched in my guard book, an indicative and seen all its results, they all seem correct, dates, hours, modes ...

Some suggestion of how to incorporate those hundreds of contacts into the book.
Thank you.

Pd: If you need the Adif file, or the result of the import, I can upload it without problems.
Thank you.

[G4POP]

All logging software relies on there at least being a call sign, date, time, band and mode so your QSO's that dont have a time are incomplete and therefore not imported

The second group that start 'Constraint failed Unique constraint failed' are a different issue they prove that you also have duplicate QSO's in your file and are therefore not imported.

The combination of the two problems with your old log software is what causes the different number of total QSO's

[ea4t]

Hello Terry.
I understand that, but in my adif files, and log, no contact is without date or time.
If you want I can send you the file for check.
The duplicate contacts, understood.
It makes no sense to make duplicate contacts.

[ea4t]

hello again.
I write again because I think I have detected the problem.
I will see if that is and I put what it was.

[ea4t]

Hello again, I have located the problem.
She was in several contacts at the time.
In those coties I had hh:m
And in few others hh::m
So it was not correct.
and after checking 110000 contacts they are already located and corrected.
The data is already correctly imported.
Thank you.