LoTW and Clublog

[F6EXV]

Terry
No dates involved.
The TX7N log extends over a 15 day period, and is closed, it will not change.
Again, I just don't know how to explain what seams to me like a very simple situation. Let me try again
I have this Log4OM TX7N log with 41,000 QSOs in it, all the QSOs are marked LoTW sent = NO
I have this Clublog adif file, and the QSO in this file need to be marked as LoTW sent = YES in Log4OM because they are uploaded to LoTW using TQSL, not Log4OM. This file has 1200 callsigns and 5,000 QSO. Every next day, I will get new adif file that will represent the newly uploaded QSOs to LoTW through an adif file created by Clublog and processed by TQSL. I will have this daily adif file available. The upload is done with TQSL, not with Log4OM

Can I import that file into Log4OM so that these imported QSO will then be marked LoTW sent = YES ?

In 6 months, all the QSOs still marked LoTW sent = no will have to be uploaded. This latter operation I know how to handle (just change the NO to QUEUED, that is simple).
My problem is : how do I import an adif file and, in Log4OM, mark the imported QSOs as LoTW sent = yes ?

[G4POP]

Can I import that file into Log4OM so that these imported QSO will then be marked LoTW sent = YES ?

No

In 6 months, all the QSOs still marked LoTW sent = no will have to be uploaded. This latter operation I know how to handle (just change the NO to QUEUED, that is simple).

Incorrect they should be marked Yes

My problem is : how do I import an adif file and, in Log4OM, mark the imported QSOs as LoTW sent = yes ?

If the QSO's already exist in Log4OM, importing the file will not change the existing sent status to Yes

If the QSO's are NOT already in Log4OM then the incoming file will add those QSO's and their LOTW sent status to the existing log.

If you had used just one program to handle your data life would be easy, like use Logger32 or Log4OM to send the data to LOTW, Clublog, Eqsl etc then there is a coordinated record.

[F6EXV]

"Incorrect, they should be marked YES".
Wrong.
They are originally marked NO = Then they must be marked queued so they are uploaded, and then marked yes.

The daily upload to LoTW comes from Clublog, because there is no other way whatsover to use Log4OM to deal with online QSL requests generated by Clublog

[G4POP]

"Incorrect, they should be marked YES".
Wrong.
They are originally marked NO = Then they must be marked queued so they are uploaded, and then marked yes.

Thats because your using Clublog to upload, under normal use they should be marked Yes but what your doing is not normal use.

Have you tried to do this with Logger32?

[F6EXV]

Well, I have no other way to upload to LoTW using Log4OM, unless I mark these QSOs one by one. Obviously, I cannot do that.
No, I have not tried to use Logger32 for that purpose.

So there is no way to import an adid file so that the imported QSOs are marked yes for LoTW upload sent ?

[G4POP]

There is no problem uploading from Log4OM to lotw direct but your choosing to do it from clublog which is complicating things, especially as it seems your not uploading every qso to lotw via clublog.

Normally users upload all qso's to lotw, eqsl clublog etc from Log4OM2 either automatically in real time or by using the Log4OM2 qsl manager in batches like once a day, week, month etc.

Using the above method the qso's are marked lotw, eqsl etc sent automatically.

Then any QSOs that receive confirmations from lotw etc are updated as confirmation received when a lotw, eqsl etc download is done in qsl manager.

If you try importing the adif file and those qso's already exist in log4om they are treated as duplicates and not imported, we try to avoid dupes!

[F6EXV]

I am more than happy to upload from Log4OM, even better.
In order to do that, I need to import the QSOs to be uploaded in the form of an adif file (the one created by Clublog for those people who have paid for a fast LoTW upload, and a paper card). But the problem remains basically the same.
Either I import into Log4OM to do the upolad within Log4OM (so the import must mark the QSOs as QUEUED)
or
I upload with TQSL and import these QSOs and mark them YES.

How do I do that ?
Is this any clearer ?

[G4POP]

Is this any clearer ?

Its been clear from the begining!

You have used an unortodox and convoluted method of uploading to LOTW due to the fact that you are doing partial uploads via Clublog/TQSL because people are paying you for fast confirmations of their QSO's

Now you have created a situation that is difficult to resolve because apparently the uploaded QSO's cannot be easily identified and seperated from the rest of your logbook entries so that you could do a bulk update.

As I have previously explained importing the ADIF file will result in the QSO's being treated as duplicates because they are already in the logbook and as such they will NOT be imported.

For us to make what you require possible in Log4OM would be a similar ammount of work to that which Lele and I did to resolve your earlier database issues before last Christmas, you will recall we spent a couple of weeks on it?

Probably the easiest way to resolve this would be:

1. Export your log from Log4OM either as an ADIF file, CSV or Excel spreadsheet

2. Then manipulate the data using ADIF master or your spreadsheet by merging the data into the spreadsheet.

3. When the data is updated save it as an ADIF file

4. Create a new/empty SQLite database in Log4OM

5. Import the resulting ADIF file into the New/Empty SQLite database created in 4 above.

Having reached a point where the log matches, use Log4OM to upload to LOTW so that the QSO LOTW sent status is automatically updated.

How you receive the requests and payments for these early confirmations is not clear, do you receive an email or text from the other station or do you receive an OQRS from Clublog or some other QSL handler?

[F6EXV]

Terry
I have mentioned many times that I get a adif file of the QSOs in question.
Just ignore anything else about Clublog.
Consider I have a adif file of the QSOs that either (I can use either method) have been uploaded with TQSL and are to be changed from "to upload" for "uploaded", or are to be marked "to be uploaded" in Log4OM, and I will do the upload from Log4OM.

When I use the QSL manager in Log4OM, I can only import from Lotw, and those imported QSOs will be marked confirmed. That is not what I want.

Can I import an adif file so as to mark the QSOs as uploaded to LoTW (those QSO are already in the log, originally marked as not uploaded) ?
The answer can only be yes or no !
If not, well, too bad. I am not asking for a rewriting of Log4OM, I just want to know if it is possible to do what I would like, because, if it is possible, I do not know how.

[G4POP]

Terry
I have mentioned many times that I get a adif file of the QSOs in question.
Just ignore anything else about Clublog.
Consider I have a adif file of the QSOs that either (I can use either method) have been uploaded with TQSL and are to be changed from "to upload" for "uploaded", or are to be marked "to be uploaded" in Log4OM, and I will do the upload from Log4OM.

When I use the QSL manager in Log4OM, I can only import from Lotw, and those imported QSOs will be marked confirmed. That is not what I want.

Can I import an adif file so as to mark the QSOs as uploaded to LoTW (those QSO are already in the log, originally marked as not uploaded) ?
The answer can only be yes or no !
If not, well, too bad. I am not asking for a rewriting of Log4OM, I just want to know if it is possible to do what I would like, because, if it is possible, I do not know how.

I have said several times on this topic

NO IMPORTING THE ADIF FILE WILL NOT UPDATE THE EXISTING QSO'S

Read my previous posts for an explanation why importing your ADIF file will not work