+ AA6YQ comments below + Database field names are not required to be ADIF-compliant. I did not change the database field names because I didn't want to break existing filters or scripts, and because I

+ AA6YQ comments below + What's the lower bound on that band segment in SpotCollector's sub-band definition file? + The sub-band definition file included with SpotCollector specifies this

Except that means it is still necessary to use the APP_DXKeeper_ form when writing SQL queries/scripts which is a PITA and makes reading or debugging queries/scripts more difficult. 73, ... Joe,

+ AA6YQ comments below There are also ADIF defined fields for EQSL_QSLSDATE EQSL_QSLRDATE EQSL_QSL_SENT, EQSL_QSL_RCVD, LOTW_QSLRDATE, LOTW_QSLSDATE, LOTW_QSL_SENT, and LOTW_QSL_RCVD where DXKeeper

+ AA6YQ comments below This morning after startup I launched Launcher. It was running but hung. I had to quit the process and restart then it came right up. Normal startup on this machine is very

+ AA6YQ comments below DXKeeper uses the application specific key APP_DXKeeper_DOK for German DOK. There is actually a standardized key for this, DARC_DOK. It would be nice if DXKeeper recognized and

It DOES let me spot a LOCAL spot though. ------ Scott Stembaugh - N9LJX radio.n9ljx@... http://sites.google.com/site/radion9ljx

I was trying to spot J5T on 24.890 and I get a pop up from SpotCollector, "24890kHz is not a valid spot frequency". Is this because it is right on the band edge? (He was working up

As Dave has pointed out to you previously, to force LotW and eQSL uploads on logging you must use <log_eqsl_lotw_qso>. To upload only to LotW you must use <log_lotw_qso> and to upload only to eQSL

There are also ADIF defined fields for EQSL_QSLSDATE EQSL_QSLRDATE EQSL_QSL_SENT, EQSL_QSL_RCVD, LOTW_QSLRDATE, LOTW_QSLSDATE, LOTW_QSL_SENT, and LOTW_QSL_RCVD where DXKeeper uses

This morning after startup I launched Launcher. It was running but hung. I had to quit the process and restart then it came right up. Normal startup on this machine is very fast -- think light

I have a RTTY WAS from 2008, would like to expand that to multiband RTTY, but hard to track right now. I can get a list of worked states on each band by filtering the log on RTTY

Dave,     Sorry, Thought I had changed the macro, I have changed it now.  I will test later today, or tomorrow, depending on time and finding signals on air. Thanks! Gordon - N1MGO

DXKeeper uses the application specific key APP_DXKeeper_DOK for German DOK. There is actually a standardized key for this, DARC_DOK. It would be nice if DXKeeper recognized and used this also. Björn

Joe,   I'm using the <log_qso> command in a macro. I use the same script to log all digital mode contacts in WinWarbler. Gordon  N1MGO

FYI, Information overload can be managed by applying filters. On very busy bands, filtering out non-alerting callsignsns greatly reduces the number of callsigns displayed. I

+ AA6YQ comments below I don't so much care about WAS "Endorsement BINGO" but do think that DXKeeper/SpotCollector should support the basic awards including RTTY (rule 9e) in the same way it supports

+ AA6YQ comments below + The N1MM-DXKeeper Gateway will send a callsign to DXView when it receives a <lookupinfo> directive from N1MM; typing a callsign into N1MM's Main window and striking your

+ Either a previous version of the WAS rules specified a QRP endorsement, or someone here asked for this capability. I don't have a problem with providing capabilities beyond an award's rules: DXLab

I don't so much care about WAS "Endorsement BINGO" but do think that DXKeeper/SpotCollector should support the basic awards including RTTY (rule 9e) in the same way it supports the other modes - Mixed