Search found 193 matches

by w9mdb
05 Feb 2018, 16:43
Forum: User Support
Topic: CQZone defaulting to 5
Replies: 4
Views: 1449

Re: CQZone defaulting to 5

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
by w9mdb
05 Feb 2018, 14:40
Forum: User Support
Topic: CQZone defaulting to 5
Replies: 4
Views: 1449

CQZone defaulting to 5

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:...
by w9mdb
15 Jan 2018, 12:29
Forum: User Support
Topic: LoTW weirdness
Replies: 41
Views: 12192

Re: LoTW weirdness

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...
by w9mdb
13 Jan 2018, 15:17
Forum: User Support
Topic: LoTW weirdness
Replies: 41
Views: 12192

Re: LoTW weirdness

May i ask when 1.31 will be available?

de Mike W9MDB
by w9mdb
22 Dec 2017, 04:54
Forum: User Support
Topic: LoTW weirdness
Replies: 41
Views: 12192

Re: LoTW weirdness

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...
by w9mdb
17 Dec 2017, 14:26
Forum: User Support
Topic: US-CA Award and Digital Mode
Replies: 5
Views: 1836

Re: US-CA Award and Digital Mode

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
by w9mdb
14 Dec 2017, 16:35
Forum: User Support
Topic: LOTW error
Replies: 1
Views: 722

Re: LOTW error

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
by w9mdb
14 Dec 2017, 16:34
Forum: User Support
Topic: LoTW weirdness
Replies: 41
Views: 12192

Re: LoTW weirdness

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
by w9mdb
14 Dec 2017, 14:36
Forum: User Support
Topic: LOTW error
Replies: 1
Views: 722

LOTW error

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 ...
by w9mdb
14 Dec 2017, 14:31
Forum: General discussions
Topic: Current V2 status
Replies: 19
Views: 42409

Re: Current V2 status

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