But...if the incoming ADIF record already has the CQ zone seems like Log4OM should not override it....especially when it's blank.

de Mike W9MDB

Example KI7FBQ was logged from JTAlert with the correct CQZone 4 to Log4OM. But Log4OM put it in with CQZone 5. I don't think qrz.com returns CQZone so there must some logic in Log4OM overriding this. I had Log4OM set up for using qrz.com in Settings 1 2018-02-05 14:20:35.5324 INFO: TCPEventManager:...

This does the county too #0 Back it up!!! #1 Open QSO Manager/QSO Archive #4 Click Field Update and click the OK on the "No rows selected" popup. #5 Under "Execute custom update query" put this update log set state=substr(state,1,instr(state,'//')-2) where instr(state,'//')>0; #6 Click all 4 warning...

May i ask when 1.31 will be available?

de Mike W9MDB

Turns out you can fix this inside Log4OM #0 Back it up!!! #1 Open QSO Manager/QSO Archive #2 Click Search Parameters at bottom #3 in the Simple pulldown select "State" and then "LIKE". Then put "%//%" in the box. Click +. Close the window. #4 Click Search at the top, then Select All #5 Click Field U...

The comments LOTW is putting in actually are within the ADIF standard.

Log4OM is not parsing the field correctly. Every ADIF field contains a length and the length for <STATE:2> is correct followed by a comment which is supposed to be allowed.

de Mike W9MD

If you download the sqlite3 command line utility you can fix this until LOTW or Log4OM fixes this.
Just run 'sqlite3 database.sqlite' with whatever your database name is and do this:
update log set state=SUBSTR(state,1,2);

de Mike W9MDB

If you download the sqlite3 command line utility you can fix this util LOTW or Log4OM fixes this.
Just run 'sqlite3 database.sqlite' with whatever your database name is and do this:
update log set state=SUBSTR(state,1,2);

de Mike W9MDB

LOTW started putting comments in their download files So when you look at statistics and awards, for example you see this IL // ILLINOIS *** NOT FOUND *** So far it's only for CNTY and STATE <CNTY:15>FL,HILLSBOROUGH // Hillsborough <STATE:2>TX // Texas So it appears the ADIF parser is not using the ...

As for your DB query problem won't an sql join work to prevent your 1M query example?
Joins are not as fast as a single table but if it makes the code easier to maintain a slight performance hit may be worth it.

Mike W9MDB