Oops...let me correct that...still broken... The pull down box on the left side is set to whatever the selection is in Confirmations when you click Select required. I could see setting the default when you pick LOTW as the Search Confirmation...but not when you click Select required. And I'd like to...

It seems a fresh download and install-over-the-top did fix it.
Seems odd but I'll have my friend try it too.

Thanks Terry,

Mike

The left side.
Click the left side pulldown to a non-default and click the "Sent" box. Then click "Select required" -- the box turns back to the default so the pulldown is useless.

Mike

If you're not going to fix the pulldown in the QSL manager so we can select a status other than the default for LOTW you should at least make the box read only since it apparently has no effect. Then all the users would have to do is try and figure out how to fix their problem. Or do you think it sh...

No...we did not change that. We were trying to fix a batch of QSO where the status was wrong. Both of your suggestions for workarounds work...but that's not desirable behavior when the fix is to make the Snet pulldown work correctly for choosing LOTW sent status. And is the text in that box wrong or...

Doesn't work on his computer or mine. Both of us using 2.7.0 I have one QSO that I marked as "Requested" for LOTW sent status and it queries just fine as Requested. Change that QSO to LOTW Sent "No", click the Sent pulldown for No, click "Select required" and the pullldown box changes back to Reques...

The LOTW upload query is a good example of the lack of normalization in the database. This query has to retrieve the entire database so it can parse the QSL field for LOTW QSO's to upload. This same every-qsl-in-a-field-regardless-of-source also slows down other queries. The lot Log4OM does this sam...

The compaction of all QSL's into one field makes for an extremely slow query. All the QSL information is in qsoconfirmations which means in order to find any particular group of QSO's...like LOTW uploads with Requested status the entire database must be retrieve and the client walks through that fie...

I just noticed a similar problem. Helping a friend and he had the JTAlert Requested box checked off...so just turned that on. Then I tried to help him upload the 90+ QSOs that didn't get uploaded to LOTW since they were marked "No" for status. Turns out can't be done in 2.7.0 #1 If you try to change...

I'd like to up-vote this. A friend of mine won't even upgrade until this is done as he is very dependent on email alerts....as am I.

I don't even run the cluster without email alerts.

Mike W9MDB