Thanks, Rich. What I was aiming for (let's use your call) is: VE1DX <--> VE3KI: 3412.8 km It worked fine as: <callsign>: <dx> But when I added the VE1DX <--> it choked. Either there are delimiters to

Additional info: It also does it when processing the LoTW QSLs, and specifically says -- is an unknown SQL command. 73, Paul VE1DX

Dave, If I use the following comment for a QSL: VE1DX <--> <callsign>: <dx> DXkeeper gives a SQL error when trying to create a .adi file for QSL printing. It seems to not like the -- part. Is there a

VE7CC-1 was down when I got in here around 13:00 UTC this AM. I see it is back up now. My node (VE1DXI) was off from about 15:00 UTC 26 March until about 14:00 UTC today, 27 March. The VE1DXI outage w

Hi Bob, The LoTW site appears to be down. I encountered what you did earlier and tried going directly to their web site with my browser . . . timed out. I believe the issue here is DXKeeper tries 3 ti

FYI.... Canada fully authorizes 5 MHz Channels On Wednesday 22nd January, the Canadian regulator, Industry Canada(IC) released a decision to allow amateur radio operators to use the 5332 kHz, 5348 kHz

I tend to agree, Dave. That is why the title is "Strange request!" I see Rich has also shown some interest, but we are likely a very small subset of the DX Labs community. Unless there are a lot more

Hi Dave, This "feature" probably wouldn't be used by many, but here goes. I have DXKeeper set to do an automatic backup on shutdown. After I am finished for the day, occasionally I want to re-start DX

Hi Rich, Is F6HKA operating a remote station in the USA via the Internet? If so (and whether or not he is would be a wild guess on my part), what should he sign? I never used a remote station, so I'm

There were several spots of K3Y/EU in the database when I added it. I did a re-compute on the DB and it now displays them as Badsource. I don't know if new spots would be filtered or not. Iain, N6ML,

Hi Dave, I put K3Y/EU in SC's special calls as Badsource. It takes it, but SC still displays it with the DXCC as EW and the Tag as Badsource. Is this because of the / in the call? 73, Paul VE1DX

Thanks, Dave. I for one will make use of the extra SQL filters. As unusual as it sounds, I used up the 16 previous ones quite quickly. There are so many useful SQL filters one can dream up, depending

Hi Steve, The DX Cluster I run has the call VE1DXI (V E 1 "DX Information") and my personal call is VE1DX. Either way, with the filters you have set, you should see 60m spots. I personally reject them

If I may offer an opinion . . . email and other "transitory" information (even mailing addresses) change quite often, while things like a nickname rarely do. Changing DXKeeper to selectively guess whi

That's one of the reasons I replaced my IC-756PRO3 with a K3. Granted the K3 is the better of the two radios in that class due to advances in technology, but I really liked the PRO3 . . . except for t

Those who use the VE1DXI DX Cluster node (ve1dxi.no-ip.ca:23) with SpotCollector may have noticed it was sporadically off and on today, with a 2-4 hour outage around 19:00 -- 03:00 UTC. This was due t

Looks to me like your email is set to HTML on Yahoo's site, so you would be getting a "full featured" email with special characters. Check this on Yahoo's web site and if it is HTML, change it to plai

I think you have found it. Generally (and I'm open to correction by those who know this package inside out), DXKeeper looks for an existing QSO with the call in question before it tries to find out wh

That's all you do, Larry. Put an exclamation point in front of the call. This causes the record to be ignored for award purposes. If, for some reason later on you want the call "active", just remove t

Hi Dave, The following Errorlog.txt has appeared twice in the last few days in my DXKeeper directory. I deleted the first one and another appeared today. I do use the QSL Msg box in the Capture window